Live data from Hacker News

Ask HN: Are there and will there be a lot of JavaScript backend developer jobs?

news.ycombinator.com

51–56 of 56 posts

Re: Ask HN: Are there and will there be a lot of JavaScript backend developer jobs?

#51
post #35

I think JS will do quite well as JS becomes the back end scripting language over time (in place of lua for example.) I don't see a bright future for ruby, I think it had some lead advantage, but RoR/opinionated-design really cut down the options for innovation with a Ruby based web dev group. It is interesting to see how diametrically opposed philosophy of Ruby the language is from the RoR community, it is like Ruby…

Python needs popular applications such as Magento, Joomla, oscommerce, etc. in PHP. Python needs better integrated with LAMP as the default in 'P'.

Absolutely agree that Python has a weak showing, but Java always had an odd disconnect with the real world too. These languages survive in every field despite relatively odd and impractical infrastructure in most due to the availablity of fresh grads that have been taught in them.

Re: Ask HN: Are there and will there be a lot of JavaScript backend developer jobs?

#52
post #22

PHP, Java, and C will probably stay around as long as their isn't a huge shift in software development, e.g. by having AI doing the development for you. JS as a backend is more of a joke, though. It has heartful followers, true. But it doesn't bring anything valuable to the table. I may be wrong (and happy to be corrected) but this was developed by people who learned the JS frontend stuff first and then didn't want t…

The killer feature (and only reason I use it) is being able to render the same templates with the same data on the server (isomorphic/universal/whatever). The result is a webpage that can do lightening-fast transitions client-side without breaking the back button.

Hm? Other languages also have template systems. PHP actually started as template system. Even today it should be possible to do inline templating stuff just with PHP (although other template languages are easier to use for that purpose). Not a huge fan of PHP either, but templating is not a killer feature. Everybody has that.

Re: Ask HN: Are there and will there be a lot of JavaScript backend developer jobs?

#53
post #37
post #22

PHP, Java, and C will probably stay around as long as their isn't a huge shift in software development, e.g. by having AI doing the development for you. JS as a backend is more of a joke, though. It has heartful followers, true. But it doesn't bring anything valuable to the table. I may be wrong (and happy to be corrected) but this was developed by people who learned the JS frontend stuff first and then didn't want t…

nodes killer feature is the (accidently) combination of good practises. And the commonjs lexical scoped module system

> combination of good practises

Other languages have that as well, although probably not the same good practices.

> commonjs lexical scoped module system

Fast googling of commonjs results in it being some kind of standard library? Not really sure what this is. Can you explain more in depth?

Re: Ask HN: Are there and will there be a lot of JavaScript backend developer jobs?

#54

I think JS will do quite well as JS becomes the back end scripting language over time (in place of lua for example.) I don't see a bright future for ruby, I think it had some lead advantage, but RoR/opinionated-design really cut down the options for innovation with a Ruby based web dev group. It is interesting to see how diametrically opposed philosophy of Ruby the language is from the RoR community, it is like Ruby…

I don't think ruby is going anywhere anytime soon. It has a strong and welcoming community; It is also very easy to get started with.

I agree with you that Rails requires following conventions but then again which framework doesn't?

Rails is a mature framework and has been widely used in production. The reason why rails succeeds is because it allows you to deliver applications very quickly to market to meet the business needs.

Ruby's philosophy is move quickly and break things, I have no doubt ruby will stay relevant thanks to the community embracing change rapidly.

Re: Ask HN: Are there and will there be a lot of JavaScript backend developer jobs?

#55
post #53
post #37

Earlier quoted context omitted.

nodes killer feature is the (accidently) combination of good practises. And the commonjs lexical scoped module system

> combination of good practises Other languages have that as well, although probably not the same good practices. > commonjs lexical scoped module system Fast googling of commonjs results in it being some kind of standard library? Not really sure what this is. Can you explain more in depth?

Node uses JavaScript witch is a simple scripting language that is event based, asynchronous, and thread safe.

In JavaScript there are values: 42, "hello", true. And objects: [list], {object}, function. And if statements ... While more stuff exists there is a consensus in the JavaScript community that they should be avoided, so you rarely see the bad parts. Then there are only a handfull of built in JavaScript functions. And there is no concept of stack, pointers or types. How the data is represented in binary vary and is very optimized.

A node script is usually a bunch of functions that are called by IO events, like a IP socket connection or callbacks from data streams, like when a buffer is filled.

Node has no standard library, just a bunch of built in modules, that are required like any other module. And Node does NOT support imports, includes, or global variables, instead you require Modules. And since modules are lexically/function/block scoped, they can only be called from within the function from where you required them. You never have to look elsewhere to see where a variable is declared, or search for places where it's used, like in many other programming languages.

Here's an example how a NodeJS script can look like:

  var socket = require("socket");
  socket.onConnection = function socketConnection(client) {
    client.onData = function dataReceived(message) {
       var sms = require("sms");
       sms.send(message);
       client.send("SMS message sent");
    }
  }

Besides lexical scoped modules in the example above there is also a "closure" of client in dataReceived from when socketConnection was called.
Post reply on HN