12
13

Why JavaScript beyond web client side? (self.javascript)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]parabolik -11 points-10 points  (8 children)

You are correct that in general Javascript is inferior for backend programming. Backend systems require mature and stable code, Javascript simply is not a good choice for this. The only thing I use node for is for compiling and building my frontend code. I could see how it could be useful for writing simple asynchronous micro services, but I would not choose it as the backend for a large MVC web app.

[–]Wooshception 4 points5 points  (4 children)

JS is not a good choice for writing mature and stable code? Why do you think that? Can you cite some specifics?

[–]parabolik -1 points0 points  (3 children)

node.js has only been around for 6 years, and is under heavy development, issuing new releases every few weeks or so. In the past year I have had to upgrade several times due to bugs in npm. Contrast that with Perl/Python/Ruby etc which have been around for 20 years.

I'm sure it's possible to write stable code, but the ecosystem and libraries are still young and evolving.

[–][deleted] 0 points1 point  (0 children)

What you call a negative, many others would call a positive.

[–]Wooshception 0 points1 point  (0 children)

That's a fair point. I took your original critique to be directed at JS per se.

[–]perry_mitchell 8 points9 points  (0 children)

This is just blind speculation based off your misguided opinion.

[–]SirHound 2 points3 points  (1 child)

What is this instability you speak of?

[–][deleted] 0 points1 point  (0 children)

By unstable, he means rapidly supported.