Geek Answers Handbook

Will Javascript V8 kill all other server-side dynamic languages? Ruby, Python, PHP?

It's all. Should it be very nice to share the same libraries on the client and on the server or not? Are JS VMs like HotRuby ( http://hotruby.yukoba.jp/ ) an alternative to the "real world" or just a toy?

PS : if I ask, this is because I would like to know this, please do not close this question, but just share your opinion.

  • I am not interested in the programming language war. Put some landmark if you know, or the pros and cons.
  • I do not compare apples and pears https://stackoverflow.com/questions/3436335/could-node-js-replace-ruby-rails-completely-in-the-future
  • I'm not a js fan
+7
javascript python ruby php
source share
1 answer

Simply put: no.

To use a longer explanation: The server-side JavaScript server may put a large dent in the scripting languages ​​used, but it will not replace them for several simple reasons:

  • Legacy - there are many code and libraries already written for PHP, Python, etc. Just as no one is in a hurry to switch to Python3, no one will be in a hurry to switch to server-side JavaScript.

  • Brainfuck - JavaScript for most people is still a big brain to code correctly. People are used to compulsory programming and "normal" OOP. JavaScript is a strange combination between very strange OOP and functional programming. Not that it's bad, I personally love him, but he turns most of the mediocre programmers. And let’s take a look, most programmers are mediocre.

  • Price - while everything works very fast, always nice. Nowadays, people are much more expensive than equipment. Turning everything into a new paradigm, or just forcing people to learn a whole new way of doing things, is just ... expensive. Very expensive.

  • Applications for killers - this is connected with number 3. Until you have a very good reason to switch to server-side JavaScript, people will not want to make investments.

In addition, to top it off, doing server-side things is so different from what the browser-side stuff does, that there is almost no imaginable need to run the same code at both ends. Even the skills needed for development at each end are significantly different.

+11
source share

More articles:


All Articles