Live data from Hacker News

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

news.ycombinator.com

1–10 of 56 posts

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

#2
As you say, PHP is pretty old and still widely used. There is still a lot of Cobol code running in the world. I would argue that there is so much inertia in programming languages that you can allow yourself the privilege of selecting strictly from which language you enjoy the most, not by trying to analyze which will provide a stronger career path.

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

#3

As you say, PHP is pretty old and still widely used. There is still a lot of Cobol code running in the world. I would argue that there is so much inertia in programming languages that you can allow yourself the privilege of selecting strictly from which language you enjoy the most, not by trying to analyze which will provide a stronger career path.

I used to be a flash developer.

It's worth considering.

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

#6
No, front-end and back-end cultures are too different. Front-end people like things that are shiny and new, the latest framework in the latest browser and it's only got to last a year at the very most before it gets re-written again (or the company is bust). Back-end people like things that are proven and stable and don't care if it's a decade old, because they want something that will last another decade. If you try and cross these streams you get things like MongoDB and Node.JS - lol.

It's why I never trust anyone who claims to be a "full-stack" developer. They will be bad at least one of them.

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

#7
As javascript has continued to crawl into many areas where nobody thought it would, my guess it could grow in the future. But it still lacks a good/popular backend framework (in node), as apposed to client frameworks.

At the same time I think PHP has a good future, where 7.0 made a really great progress in performance. Laravel is awsome for web development.

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

#8

As you say, PHP is pretty old and still widely used. There is still a lot of Cobol code running in the world. I would argue that there is so much inertia in programming languages that you can allow yourself the privilege of selecting strictly from which language you enjoy the most, not by trying to analyze which will provide a stronger career path.

You can't compare PHP and Cobol. PHP is insanely popular (#3 globally) and will be for a while. Cobol isn't even in the top 20.

http://pypl.github.io/PYPL.html

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

#9

As javascript has continued to crawl into many areas where nobody thought it would, my guess it could grow in the future. But it still lacks a good/popular backend framework (in node), as apposed to client frameworks. At the same time I think PHP has a good future, where 7.0 made a really great progress in performance. Laravel is awsome for web development.

Express seems pretty popular, it has stuff for routes, templates etc... Bit like Backbone for Client, without the HTTP stuff

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

#10

As you say, PHP is pretty old and still widely used. There is still a lot of Cobol code running in the world. I would argue that there is so much inertia in programming languages that you can allow yourself the privilege of selecting strictly from which language you enjoy the most, not by trying to analyze which will provide a stronger career path.

You can't compare PHP and Cobol. PHP is insanely popular (#3 globally) and will be for a while. Cobol isn't even in the top 20. http://pypl.github.io/PYPL.html

Searches on Google don't mean anything. COBOL programmers are from an era where programming wasn't just cut-and-paste-from-Stack Overflow.
Post reply on HN