4 ms·
If you're planning to write for the web (who isn't), then I prefer javascript for 2 simple reasons: 1. Unless you use Flash, you'll probably have to use some
by edw519 17y ago
If you're planning to write for the web (who isn't), then I prefer javascript for 2 simple reasons:
1. Unless you use Flash, you'll probably have to use some javascript anyway if you want any logic on your client.
2. You can click View:Source on any web page to see the javascript running that page. You'll have millions of examples of source code along with that code in action right now on your machine. A live example is an excellent learning tool.
You can also use javascript for your server side logic, but that's another debate altogether. If you build some pages that do something first, you can worry about the back end later.
- gdp 17y agoI can't help but notice that this does nothing to answer the question, which was about how to decide between any two languages, with Python and Ruby given as examples, rather than "What language should I use for web programming?", which appears to be the question you have answered.
- jhancock 17y agoThe question is too open ended if you take that approach and does not allow for concrete answers. The OP does allude to the fact that he wants to build a webapp and does mention ruby and python, both decent choices. A lot of the answers here suggest that either is a fine choice, which perhaps is all the OP needs to hear.
- gdp 17y agoI really have to call you on this one. Usually I would just let it go, but really, this has just missed the mark. You're suggesting that the presence of certain keywords in a question permit you to totally rephrase that question and then answer that instead? I'll quote from the post: > The author discusses choosing the "best language for the task." That is something I see discussed quite frequently. I know there are languages that are most commonly used for certain tasks, but how do you decide between two similar languages? That was the question being asked.
- jhancock 17y agoI really wanted to use javascript (client and server) for my new webapp. But alas, the various server-side frameworks aren't quite ready for me yet. I think a pure client js + app server js + js db would be fantastic. Even though the various javascript server libs/frameworks are maturing very fast, I cannot afford to toss perfectly good high level solutions that exist with something like merb: production server process management, integrated release scripts, session management and authentication, etc... If you go with js server side at the moment, you get to roll your own for all this. I want this to be the answer, but for right now, I can't afford to cut my teeth on it.