[jomamaxx]

This is not true.

It's far more used than you think.

I just had to use some of Nuance's new voice recognition technology - the entire thing except for the voice libraries are in Node.

I think it's a trend, not a fad.

It's not magic, and there are drawbacks ... but Node isn't going anywhere, it's here for a while.

JS is a natural fit for the web and with Typescript now it's made advances.

[merb]

> Nuance's new voice recognition technology - the entire thing except for the voice libraries are in Node

That basically means it's not even built with it. The only thing it provides are JS bindings. Nothing more. Something like JNI. And I basically can confirm that their voice recognition (Dragon) was NEVER written in node and NEVER will. It's written in C. And they provide bindings for C# and Visual Basic and C++, however they have ActiveX in place which means that there are way more languages that can use it. I guess at some point they even added Node bindings.

http://www.nuance.com/ucmprod/groups/dragon/@web-enus/docume... http://www.nuance.com/ucmprod/groups/dragon/@web-enus/docume...

[jomamaxx]

Of course Dragon is not written in 'node' - nobody would write such a thing in javscript, moreover, if it were, it would be described as 'written in JS' not 'Node'.

Second - what you refer to as 'just some bindings' is false.

The Nuance product I have access to (NTE) - is probably something you don't have access to, as very few do.

There's a huge pile of code written 'on Node' because just as JS would be the worst choice of languages to write Dragon in - C#, C++ or Java would be the worst choice in languages to do the stuff they did using Node for, which has a mostly to do with HTTP services, file management, versioning, REST api etc.. The choice of Node + platform libraries made perfect sense for Nuance - and it's perfect validation of Node.

I'll wager you any amount of money that Node is going to grow quite a lot over the next 4-7 years to the point wherein it will be seen as de-facto institutional.

Node has flaws, many of them due to JS, and they have some ugly new NPM fragmentation issues, but it's only growing to grow. Of that there is no doubt.

Node will replace a significant chunk of Java and more-web oriented backend stacks in the years to come.

We've even replaced a bunch of Python scripts with JS, not because JS is better than Python (Python, syntactically is superior) but because of the libraries and platform opportunities. JS/Node is a much more natural fit for large, async tasks than Python.

Finally - the ability to use the same object mode on both front end / back has significant operational advantages when it comes to reuse of components, which we do quite a lot - and don't have time to deal with various bindings.

Node is 'here to stay' as much as any other technology is/was.