What in god's name is the point of NodeJS???

What in god's name is the point of NodeJS???

Attached: unknown.png (586x239, 60K)

Other urls found in this thread:

node-os.com/
twitter.com/NSFWRedditGif

JavaScript but not in a browser.

So that we can make NodeOS

Attached: received_421382251724402.jpg (946x655, 113K)

Literally a browser for each instance.

Literally wrong

Attached: received_1505885019521163.jpg (720x1280, 45K)

node-os.com/

As scripting languages go, JavaScript has benefited from decades and hundreds of millions of dollars put into making it performant. It'll never be as fast as Java or a real statically typed language but it kicks the shit out of Ruby, Python, et al. Couple that with the fact that you can share code between the browser and server. And then consider the event driven non-blocking IO. I rarely use node but I see it for what it is. How could it not have been successful?

php is evil and use the devils syntax backend dev should be ez like the internet so people in the community can get good jobs

I guess it's good if you're not smart enough for multithreading

It is the second greatest invention behind javascript itself. Node has taken over the backend, the desktop, the command line, and eventually, the world. It has enabled fast, cross-platform applications such as vscode to be created in a timely and efficient manner, while enabling a level of customisation and accessibility that has never been seen before on a desktop application.

Node is a revolution in backend web servers. It pioneered the use of asynchronous callbacks now copied by all other web servers. The performance of this approach is unrivalled, and only now are the competitors catching up. Node allows developers to use the programming language they love on both the front end and the back end, creating efficiencies that have never been seen before in the world of computer programming. Node is the current, Node is the future. Where are you going today?

holy shit

same language and libraries between front and backend, native support for the defacto data transfer schema JSON

This

>It pioneered the use of asynchronous callbacks
No, it did not

>It pioneered the use of asynchronous callbacks
>because it couldn't handle async like a normal person

It's almost like Erlang didn't predate it. And somehow it goes fine without this callback hell, and manages to actually support computers built in the last ten years due to SMP.

>defacto data transfer schema JSON

It's a bit like saying that a toilet brush is the de facto standard way to eat shit.

Whats wrong with json?

overhead to look nice

> but it kicks the shit out of Ruby, Python, et al.
But not LuaJIT, which was developed by a single fucking person.

>overhead
doesn't xml have even more overhead?

Haha BTFO

did i say xml is good/better than json retard?

are there any other data exchange formats?

the better python

There's binary shit like messagepack but it's really just a "better" "faster" json, not fundamentally different.

Are you not sufficiently fed up with using JavaScript on your clients? Well, now you can use it to make all your server infrastructure too!

Nodejs is built on c++ though

And only one single person uses it

Because it is a much simpler language and even less appropriate for serious development. Creating a JIT compiler for Lua was pointless in the first place.