|
I was wondering why will anyone (or any group) even attempt to write a programming language. Since they don't get paid for it, i really wonder why. I mean perhaps yes .NET is written by MS people who do get paid. but Do the people that write java even get paid? |
|||||||||||||||||||
|
|
It depends on the situation, but it's generally one of a few things.
Often the languages are developed for to solve a companies own problems, and then released for free to build up a community, it's always nice to have other people writing libraries for you. Also, you mentioned Java, IIRC, SUN's initial goal with java was to create a language that would gain good support in the enterprise market, and leverage the SPARC processors better threading scalability to show that it's a better platform for Java, then use this to sell SUN hardware and software platforms. This is similar to MS and the .net framework, but with less clear plans, since SUN's plan was based on perceived hardware advantages that just didn't seem to carry through. |
|||||||||
|
|
Yes, the people at Oracle who work on Java undoubtedly get paid. So do the people at Google who work on Go, and so on. During early development, quite a few people probably work on languages without getting paid anything. In most cases, it either develops into something that at least starts to break even, or else the people find something else to do with their time. No matter how dedicated somebody is, most like to eat at least once in a while, so making some money becomes important at some point. Note, however, that making money may not be particularly direct -- even when/if development of the language and/or tools is unpaid, the author might well write books, magazine articles, and give presentations to make money, and sales of those will depend on the popularity of the language. |
|||
|
|
|
I write languages because:
Scads of software, not just compilers and interpreters, are written on speculation and/or open-sourced without even the hope of future financial gain. It's just one of those things that passionate programmers do. People like using free tools when they can get them, which is why free (speech as well as beer) languages are generally more popular than proprietary ones. If you want to popularise software you've made, reducing the barrier to adoption is the first step. |
|||
|
|
|
Knowledge. By writing a programming language, they're in a better position to understand the shortcomings of other languages of the time, and how they can be improved on. If they get it right they also end off with a useful tool that can make future tasks easier to complete or more interesting. They may also do it purely for the sake of doing it. The intellectual challenge is often enough reason for many people to put in the work when there is little or no personal financial gain to be had... |
|||
|
|
|
Some developers just write a language to boost their ego. And then I guess it belongs in the "what a human has to do" category like planting an apple tree, growing a kid, building a house, writing a compiler etc. And of course all the other good arguments that have already been posted. |
|||
|
|
|
I'm designing a language myself (for fun) and I can only answer to my own reasons:
That being said I do recognize that it most likely a futile effort, the odds of creating a mainstream language is diminishing small, but what the heck, so long as you're having fun right? :) I'd also hazard a guess that the most common reason to build a programming language (unless you're being paid to do so) is pure geek cred and a neo-nerd desire to prove one self smarter than everyone else (not mine though ;) |
||||
|
|
|
Quite often its for the same reasons anyone creates any tool. To server a specific purpose that existing tools don't quite work for. Or to put it in other words "to scratch an itch". There are probably hundreds of documents you could read from authors of recent languages explaining their motivation. Here are just a few of the ones I've read in the past few years (and recall off the top of my head): |
|||
|
|
