[Rauchg]

Our focus is on empowering the realtime JavaScript cloud with its rich module ecosystem.

With the advent of microservices, code will become more succinct. Your backends will be aggregations of small functions with clear inputs and outputs.

The syntactic differences between languages will matter less. Our bet is that JS has the largest and most prolific community!

[q3k]

> Our focus is on empowering the realtime JavaScript cloud with its rich module ecosystem.

I'm sorry, but that's just meaningless buzzword bingo.

[8note]

translation: they use websockets on AWS with insane numbers NPM modules.

[williamcotton]

Actually, I think the issue is that you just don't understand the meaning of those words.

The "rich module ecosystem" he is speaking of refers to npm. With node and npm it is trivial to install a few modules from the command line, write up a custom server, and very quickly have yourself a dynamic web page or API.

The "realtime JavaScript cloud" is basically any node application running on a service like Heroku or with any number of hosts and providers ranging from self-managed VPNs to esoteric AWS services. Applications that run on this realtime JavaScript cloud are incredibly portable as engines can be fired up and torn down very quickly across both server-side and client-side environments.

This service that he has been a part of creating does exactly this. It empowers the user by streamlining existing development processes.

I would say that his sentence is rather meaningful contemporary industry jargon.

[q3k]

I do understand them exactly the way you explained.

However, they're still a buzzwordful, dodging, non-answer to the relative parents' very simple question. They're a reiteration of the most basic, marketing-level bulletpoints on why node.js and microservices are so wonderful! that barely scratch the surface of real-world software complexity.

[williamcotton]

I'm gonna go further: that is actually a fantastic mission statement!

I believe that it is very important to have goals that are simple in definition. It can really help the cause if the ultimate meaning is somewhat allusive. The act of interpreting the mission statement bakes in a dynamic element that can help keep an organization from getting stuck in place.

That I can interpret this mission statement in a verbose, complicated and applied manner is an example of its utility.

[bufo]

How are you thinking about latency in an environment where there's a waterfall of Now function calls? Will Now functions calling over Now functions naturally get cached on the same server?

[Rauchg]

There's no explicit concept of "now functions". You simply deploy HTTP/2 services to the cloud.

HTTP/2 significantly improves performance by introducing multiplexing and header compression. There's no need to introduce new concepts or APIs. REST away!