I'm baffled. A random list that links to a few most-starred node app got 50+ upvotes in 2 hours on HN and is currently No.1. First commit 3 days ago. I fail to see how it's awesome.
I was wondering that too. Either someone figured out how to game the HN algorithm, or the term "curated list" really does have some magic clickbait properties…
That's basically how the whole javascript community works. There are tons of lists with random links (usually most-starred, yeah), which doesn't make a lot of sense, but they have tons of stars and attention.
Do they help people? Yeah, some of them definitely. Are they awesome and must have to get familiar with? Barely.
From my short experience working with other communities is very different, they are much more pragmatic and sceptical (worked with Go and Elixir a little bit).
I think it's just people who use the upvote button as a "save for later" functionality. Also, if it's on the front page it might get the boost to make it really useful.
It feels like this and the numerous other "awesome" lists which claim to be curated, are curated in only the most trivial sense: perhaps someone looked to see if each new entry in some plausible way is in the right general category of thing, i.e. is not a random unrelated link. For example, this one looks like a list of open source applications that could be found or were submitted so far for inclusion.
I don't see any evidence on this one or any other of any genuine curation, which would be characterized by saying "no" to some of the possible candidates.
Unfortunately the words awesome and curation have so little meaning among lists of programming-related things, that it would probably be a waste of time for someone to actually do that, and would possibly generate hard feelings from whatever projects end up in the "no" pile.
I always wonder what gives authors of these curated lists the authority to be curators? Are they like, experts in the specific domain? What is the curation process? It's difficult to take them seriously unless these questions are answered.
Why does their need to be an authority? If somebody posts a bad list or curates against your interests, you could leave a comment or suggest a better list.
I think Node.js and Javascript have democratised development like any other tool to date. Along with web technologies. Node.js is not usable for systems architecture, Javascript is not a systems language, not a scientific/maths tool, etc. But it is excellent for highly available architectures or for application development.
> 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.
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.
Node.js deserves its buzz.
I worked in very serious business in java and since I have switch to node and js clients, things are so weirdly easy and powerfull.
Keep upvote, the world need to know!!
35 comments
[ 3.2 ms ] story [ 89.1 ms ] thread</sarcasm>
Anyone enlighten me?
https://hn.algolia.com/?query=curated%20list&sort=byPopulari...
Do they help people? Yeah, some of them definitely. Are they awesome and must have to get familiar with? Barely.
From my short experience working with other communities is very different, they are much more pragmatic and sceptical (worked with Go and Elixir a little bit).
https://github.com/sindresorhus/awesome
I don't see any evidence on this one or any other of any genuine curation, which would be characterized by saying "no" to some of the possible candidates.
Unfortunately the words awesome and curation have so little meaning among lists of programming-related things, that it would probably be a waste of time for someone to actually do that, and would possibly generate hard feelings from whatever projects end up in the "no" pile.
"No" is hard.
After looking arround for a while, we decided to make what we found public.
npm OTOH needs to die a quick and very public death.
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.
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...
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.