2 ms·
>We are speaking about languages, not which implementations are available. We are speaking about the adoption of languages, though ("Sadly it never got a big n
by coldtea 6y ago
>We are speaking about languages, not which implementations are available.
We are speaking about the adoption of languages, though ("Sadly it never got a big name sponsor to push it."), not languages in abstracto, and for that available implementations matter.
>Are there are free tools for becoming a mechanic? No, they got to be paid, either new or used in some form
Which is neither here, nor there. Things are different for programmers, where there are free and/or libre tools, and people have come to expect them and even prefer them.
- pjmlp 6y agoLanguage adoption was already a thing before the rise of GNU and BSD in the late 90's. I will love to see the world where such programmers get paid 100% the same way they are willing to pay for their tooling. Exactly the same way.
- coldtea 6y ago>Language adoption was already a thing before the rise of GNU and BSD in the late 90's. Yeah, but not for Eiffel :-) >I will love to see the world where such programmers get paid 100% the same way they are willing to pay for their tooling. Aside from those language devs getting paid (which core dev teams for otherwise given for fre/ FOSS languages like Java, C#, Swift, Go, etc also are), what else would change? Paid/proprietary is orthogonal to better languages/tooling. If popular compilers/apis were paid, we could just as well get the same commercial crap, lack of interest, bloat, needless novelty, etc. that we get with most paid proprietary software and hardware. And even worse, since they would be both out of reach for amateurs/students/developing world/etc, and crappy "enterprise level" for the rest, driven by what sells to pointy hair bosses, not programmers.