I agree that it would be good to have a list of languages categorized by freedom status and typical use cases for each language. The list would not be comprehensive, but it might still be a good thing to have as a quick reference. Who has ideas about the right way to start building and hosting such a list? It would be an effort similar to the Free Software Directory, but with a different focus and different metadata.
-Alan Beadle On Wed, Feb 3, 2016 at 3:39 PM, aurelien <[email protected]> wrote: > aurelien <[email protected]> writes: > > > Fabio Pesari <[email protected]> writes: > > > >> On 02/03/2016 09:04 PM, aurelien wrote: > >>> Sorry, I was thinking that programming language are under license like > software. > >>> > >>> So we can learn any programming language without risk in time to see it > >>> becoming more (close, proprietary, restricted ...) than another one? > >> > >> Well, for starters I would avoid languages tied to specific proprietary > >> platforms like Swift, even when their implementation is free, and those > >> languages whose official implementations have some proprietary parts > >> (like D, whose backend for DMD is nonfree), because that shows just a > >> plain disregard for the community, if anything. > > > > So it is possible to make difference between programming language. > > > > Maybe it should be great to have a table to help people. > > > > Like: > > > > > + as says Kos Ros > >> - The language's standard (or specification) may be nonfree. > >> - The language's compiler or interpreter may be nonfree. > >> - The language's toolchain may contain nonfree things. > _____________________________________________________ > Language|implementations|standard|compiler|toolchain| > Swift |proprietary | | | | > C | | | | | > Guile |free |free |free |free | > Go | | | | | > C++ | | | | | > C# | | | | | > .net | | | | | > > > -- > Aurélien DESBRIÈRES >
