Ask HN: How much JavaScript do you know as a back end dev?
Does it make any sense being a real full-stack engineer? Client-side JS is getting more and more complex with all that AngularJS/React etc stuff, it really pushes the limits of the one-man show approach for web development. How many JS do you know as a web/backend developer?
16 comments
[ 5.0 ms ] story [ 46.4 ms ] threadHow well does node scale? It's running in one thread, and from my use (a very small amount of experimentation and reading), it doesn't look like it could handle more than a few hundred concurrent users without stringing together some more robust queuing outside of the node code.
Some of the services I've built in Node.js handle 1000 req/s fine without the need for multiple instances or threads.
At the very least, learn some basic VanillaJS, jQuery, and lo-dash. You can get fancier later.
I spend a lot more time improving my javascript skills now.
The answer is NO! JS is a dead end. JS is the shit of the shit. Sooner or later people will realize that JS is just an abomination, something that shouldn't even exist in this world.
@omegaEpsilon I with I could downvote you.
Best regards.
Most of the really truly shitty parts of js development are caused by the lack of cross-browser standards.
And JavaScript, of course. Usually these are titled "JavaScript Developer" but they really mean "CoffeeScript Developer" and no thanks.
All of the opinionating is really to say it only makes sense if it's what you want to do. I happen to like programming (including JavaScript) so I do back and front end. If you don't like JavaScript don't do front end because it can and will get complex, and JavaScript doesn't help you manage complexity.
That said, if your plan is to work on web applications, the more JavaScript you know, the more valuable you'll be (in theory) to your employer/client.
tl;dr maybe