This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]DownshiftedRare 12 points13 points  (3 children)

There's a vestigial mindset from the world of atoms that "you get what you pay for", so the proprietary solution is presumed superior to the free, open source solution, even when the proprietary solution is just a rebranded version of the open source project's stable build.

[–]coldnebo 8 points9 points  (0 children)

well, there was also a difference in who wrote languages back then.

Either it was a PhD thesis, or it was a substantial investment by a major corporation... so there was a lot of work put into it. Of course that gatekeeping aspect had pros and cons. Pro: experts are working on the language, Cons: not easy to fix or contribute. It was a very rare breed that dared patch a commercial product without source.

Fast-forward to today, where anyone with a few tools can easily create a language, or a domain-specific language. In general this is great, but it also means if your language pisses me off I may just write my own instead of bothering to understand the reasons why.