Looks like there be will no monetary incentive in inventing a very innovative languages when the big guys can just come in and re-implement it and not pay a cent.
Looks like there be will no monetary incentive in inventing a very innovative languages when the big guys can just come in and re-implement it and not pay a cent.
I will be astonished if you can cite a single example of a programming language whose inventor was inspired by the possibility of language licensing revenue.
Note that implementation licensing revenue does not count, as implementations are covered by copyright.
Not completely regardless of the designers' wishes. If the language designer never publishes, then he or she won't have to worry about re-implementations. Publishing is by definition (and should be) a relinquishment of some amount of control.
TeX has the same concept with the TRIP test.
The concept doesn't even make sense. Do you pay someone to let you speak English? Why would you pay someone to let you "speak" any other language?
Sometimes language implementations are the product - things like R, Matlab and Mathematica are close examples. What if I figured out a much better programming language for Finance software and would like to prevent every other company from implementing it?
This debate is far more complex than what people think.
How could you patent a language? What are you patenting? The compiler/interpreter? The context-free grammar (assuming it has one)? The language specification?
If the specification, then you really mean a copyright, not a patent, because a language specification is just a description of a language, and you can't patent that. But just because you've placed a copyright on your description doesn't mean you hold a copyright on anything that anybody creates after having read that description - that would be ludicrous!
Sure, we can talk about the compiler/interpreter itself, but that doesn't prevent someone else from going ahead and creating a completely separate compiler that implements the same exact specification (look at the GNU Compiler Collection, more commonly known as gcc).
The only mention I can find of the incident you seem to be alluding to is a brief, vague, and un-sourced mention in a text file dating to 1991[1]. I'd be entirely unsurprised to learn that there is far more nuance to the story than what you and said file state, or that the incident was largely the result of a game of telephone.
[1] http://progfree.org/Copyright/against-user-interface-copyrig...
If you ship a language with implementation and would like to prevent others from implementing it, you should not be able to and fortunately even under US law it seems you cannot.
The motivation for a state-provided monopoly on "inventions" was to foster innovation (and we should be clear this institution is a state intervention in the market and has nothing to do with "natural rights" and such). The ability of patents to provide society with this benefit is debatable but fortunately there's clear consensus that patenting/copyrighting/owning ideas is bad. And a programming language is essentially an idea rather than an artifice and it certainly seems intuitively obvious that giving people ownership of language would get really nasty, really quickly.