33 ms·
“Node.js is one of the worst things to happen to the software industry” (2012)
- bryanrasmussen 10y agoI am certainly willing to entertain the notion that async models do not map naturally to most peoples' brains and as a consequence the callback style of concurrency might just be really difficult to handle. On the other hand the writer admits it may just be them not being able to understand it, which I think is also reasonable given that many people have managed to do more complicated stuff in much less than 2 months. This post is a land of contrasts, in short.
- catnaroek 10y agoYou can interpret the question of whether an abstraction “map naturally to most people's brains” in two different ways: (0) Is it easy to understand how the abstraction works in principle? (1) Is it easy to actually use the abstraction to build large robust systems? Clearly, (0) is a necessary precondition for (1). But it's not sufficient. Pointer arithmetic is an example of an abstraction that's easy to understand “in principle”, yet hard to use right (for “most people”, anyway). I'm afraid the same is true of explicit continuation (“callback”) passing. Programming with tools that only work “in principle” is hell.
- aangjie 10y agoNot sure, why this is getting downvoted.. It's very sensible and the poster provides a valid example.
- andrewmcwatters 10y agoAs much as I love Node.js, I also love this post. It screams the ever-repeated viewpoints of the experienced and tired developer. There isn't enough of this on HN.
- vpb 10y agoAlmost all pages of cat-v.org read like that. It's a good read. Most should be taken in a light hearted way - it's just software, after all. People unfortunately tend to get outraged by it. Also unfortunately, the original author, Uriel, passed away a few years ago. If you enjoy it, try taking a look at suckless.org Most pages in cat-v (and suckless) tend to favor the Unix way, small connecting components communicating through pipes. It seems sensible to me. It's comprehensible, it's easy to break down and analyze stuff when it's breaks. I never dabbled in Node.js - js is not my favorite language - but it does looks like complex and hard to understand its internals. Maybe it's not.
- aaronpk 10y agoGreat line: "The only thing that matters in software is the experience of the user."
- Ericson2314 10y agoUh, it's an odd way to end a rant on software architecture. How about: "The only thing that matters in software is abstractions/interfaces". The end user only sees the top interface.
- jdavis703 10y agoSome of the software I've had to maintain had the best UX, but winds up having the shittiest code underneath.
- hollerith 10y agoI would consider that good news (if the problem domain is important enough) because that means that the only thing left to do is write a better implementation.
- Unbeliever69 10y agoThere is good meme potential in this..."The only thing that matters in software is ___________." The only thing that matters in software is an MVP that doesn't suck so much that it can't be productized.
- dschiptsov 10y agoThis is exactly how you get professionally marketed crap like Mongo, Node, Hadoop, you name it. It is a fast-food way of building software - cheapest processed shit wrapped in a good SEO and naive user experience (quick and rewarding installation and effortless bootstrapping of a meaningless hello-world - I am so clever meme). What matters in software in the long run, be it an application or even a programming language, is appropriate design decisions and strong emphasis on design around protocols (by duck-typed interfaces), using declarative (instead of imperative) mostly-functioal paradigm, bottom-up process with focus on modularity and code reuse, while sticking to the standard idioms and principle of less astonishment. This is what is still being taught at MIT, and this is how the internet works as a whole. 99% of Node or PHP code is a toxic amateurish crap, precisely due to ignorant over-confidence of the coders and lacking of proper CS education about right principles and programming paradigms, importance of louse coupling and proper encapsulation, which leads to modular, share-nothing, mostly functional designs with emphasis on immutability and persistence (that's why Clojure is so good - it has been, like Erlang, well-researched with tons of good stuff borrowed form Common Lisp). Erlang or Haskell or Scala or Swift or Golang are on another side of the spectrum, which could be characterized by discipline of sticking to the right principles and rigorous attention to details (of which Haskell might be a bit too strict, but Erlang or Scala just right). BTW, these observations about the impact of a proper design, based on right principles, which have been made almost 20 years ago still holds - http://norvig.com/java-lisp.html http://norvig.com/java-lisp.html Today we could state the same for Python3.5+, which, finally, evolved to be so carefully refined as old school Lisps, but emphasizing that Python3 is a prototyping language, while CL is both prototyping and implementation language. No sane person should even touch PHP or Javascript or any other crap with implicit coercions, error supressions, etc, designed by amateurs (hello, MySQL, Mongo, Hadoop!) like one avoid chap processed junk food or drugs.
- Ericson2314 10y agoI dislike shitty languages and successfully avoid using them myself, but I do have to be a bit happy with NPM ecosystem teaching people to reuse more code.
- overcast 10y agoWhile there is no arguing the pitfalls of dealing with Javascript. As a one man team, to build a product with the same language on the backend, that I've already been using on the front end. Is awesome. The ability to fire up a Node.js project on a server is even easier than a PHP one, which is arguably why PHP took off in the first place. And like you mentioned, I think the NPM system is awesome, super easy to use, and a voracious community. Sure there is TONS of not nice things about JS, but it's slowly evolving to be better(ES6 + Promises), and it's not going anywhere anytime soon.
- bigtunacan 10y agoThe only way to avoid using shitty languages would be to stop programming altogether. I have found in my experience a pattern that repeats itself. 1) I find a language (B) that I think is great because it solves X problem with the language (A) previously being used. 2) I use that new language long enough that eventually I learn it's pitfalls and hate it. 3) Switch to language (C) because it fixes problems found in language (B). Eventually this loops.
- Ericson2314 10y agoI'm sorry that's been your experience. I've been using Haskell for 4 years, Rust for 2, happy with both. Anything I don't like other people usually don't like and is fixable.
- andrewprock 10y agoFor years I was stuck in a cycle: A->B->A->B ... Where A was C++, and B was Python.
- PeCaN 10y agoThere are less shitty languages. I'd consider mine to be OCaml and Perl (and Rust is growing on me, but I might be in the first phase above). I think, ultimately, this just boils down to “know a lot of tools and use the right tool for the job”.
- sownkun 10y agobit of an overstatement if you ask me
- maitredusoi 10y agoLove that post so MUCH !!!!
- lcfcjs 10y agoFuck off
- SimeVidas 10y ago4 years old?
- deleted 10y ago[deleted]
- rdtsc 10y agoI usually ask people to explain why they picked or like (or dislike) a particular technology and that surprisingly tells quite a bit about their proficiency level. At least in interviews I found it tells a lot more about their proficiency than say knowing how to invert binary tree in under 20min or solve a digital circuit diagram in with object oriented principles. Node.js is a technology that raises red flags when someone advocates it. I've heard stuff like "it's async so faster", "it makes things non-blocking so you get more performance not like with threads", "you just have to learn one language and you're done", "...isomorphic something..." When digging in to discover if they knew how event dispatching works or how these callbacks end up called data comes in on a TCP socket, and there is usually nothing. The other red flag is the community. Somehow Node.js community managed to accumulate the most immature and childish people. I don't know what it is / was about it. But there it was. Also maybe I am not the only one, but I've seen vocal advocates of Node.js steam-roll and sell their technology, often convincing managers to adopt, with later disastrous consequences. As article mentions -- callback hell, immature libraries, somehow the promised fast performance guarantees vanish when faced with larger amount of concurrent connections and so on. I've seen that hype happen with Go recently as well. Not as bad, but there is some element. Now you'd think I am 100% hater and irrational. But one can still convince me that picking Node.js was a good choice. One good thing about Node.js is it is Javascript. If there is a team of developers that just know Javascript and nothing else. Then perhaps it makes sense to have a Node.js project. Keep it small and internal. Also npm does have a lot of packages and they are easy to install. A lot of them are un-maintained and crap but many are fine. Python packaging for example used to be worse, so convincing someone with an "npm install <blah>" wasn't hard.
- micaksica 10y ago> If there is a team of developers that just know Javascript and nothing else. Then perhaps it makes sense to have a Node.js project. Keep it small and internal. If you have a team of developers that know just JavaScript and nothing else, you are probably dealing with 100% front-end developers that have little to no understanding of systems programming and what you need to do to be performant and secure outside of a browser. This leads to a lot of issues with security in the Node.js ecosystem, and is one of the reasons I have a job.
- ralusek 10y ago"The async-style of programming is almost entirely inaccessible to my brain" Proceeds to write article shitting on language which relies on this.
- PeCaN 10y agoMore like “the world's worst implementation of asynchronous programming is shitty and didn't learn from its predecessors”.
- yoshuaw 10y agoHere's the post by Ry that was supposedly deleted: http://tinyclouds.org/rant.html http://tinyclouds.org/rant.html The point I took away from the post is that all abstractions carry a cost, no matter how elegant. Not "Ryan Dahl hates Node.js". But sure. Seems the author is intent on complaining and that's cool with me, but if you're doing Node then yeah don't let people like this get you down. Node's fast, Node's flexible and has so many users that virtually any abstraction you like is available through npm. Callbacks are part of core because it's the lowest common abstraction for Async. Node is not Python. Tired devs can complain all they like, but that doesn't make them right.
- oolongCat 10y ago>Tired devs can complain all they like, but that doesn't make them right. But don't you think this is the very reason why we need to worry about these issues. Us developers are tired, its not right, this is something we all love doing, and I want more people to love this industry and we cant afford to throw simplicity in the garbage, we need to spend some effort in to making things easier for the people who will come after us.
- sotojuan 10y agoIf you're gonna fall of the cat-v bait and try to "make things right" then you pretty much can't use any language except minimal C or Go. Their page on Java (what people in this thread propose) is way longer.
- sebringj 10y agoThe number one issue I've found with Node.js is when developers make things overly complicated for no apparent reason. The bar may be too low to get in so possibly you'll get a higher degree of poor design decisions. The second would be the overuse of build scripts in that the build seems more complicated than the app in both time to get the thing up and complicated chaining steps. I've not had much fun debugging grunt, gulp or webpack in some of these fortune 1000 projects and I have a hard time wanting to give a shit about knowing them in great detail as the app should be the focus. The parts of node that I most like are the core libraries that come with the install. When I try to stick with those as much as possible rather than using some half-baked npm module for every whim, I have a very pleasurable experience. The async/wait and promises, etc along with piping streams are quite elegant in how modules can be snapped together like lego pieces but I find that people fuck it up terribly when they half know it as I initially did and it becomes akin to the messiness of es5 callbacks. It does take some time to really utilize async well so I would recommend to read up on those concepts in great detail prior to jumping in. Please npm responsibly.
- nodenope 10y agoEverything in node is just slapped together with no rhyme or reason. npm module quality is piss poor - even the flagship express web server where nothing works out of the box. God help you if you find a bug in a node core library - the typical reaction is that developers now depend on the buggy behavior and as result it won't be fixed. I've returned to sane programming languages after using node for years and I don't miss node's async nonsense where you can't perform a computation without halting all users of your application without performing major programming gymnastics.
- sawthat 10y agoYou say you are over node, but I don't think you are. You need to let go and move on.
- sebringj 10y agoIt would be nice if there were build warnings npm acceptance would give you so you had the chance to clean up things, such as build tests etc and also a recommended standard way to build them. Then if npm developers were lazy in that sense and letting the warnings pass regardless, when you install an npm, it would give you a warning, "this asshole put in a shitty module" or something more PC.
- zumu 10y ago> As soon as I wanted to write any non-trivial code to read stuff from a database and do something with it, I got stumped - I didn’t know how to proceed. I could write some code, but it would turn out very ugly. I couldn’t write code that was pleasing to read (and it certainly wasn’t pleasant to write). When this was written, he had point, but with es6 I don't think this is a problem anymore. Accordingly, I don't think this stands > You lose expressiveness Arrow functions and destructuring cut down on boiler plate significantly.
- dang 10y agoThis post is baity but the thread turned out to be rather good, so let's try turning off the flags on it. If it ends up a flamewar we'll have to put them back on, so if you comment here, please keep the discussion thoughtful! Btw, the top bit of the article is an HN comment by uriel from 2012: https://news.ycombinator.com/item?id=4495305 https://news.ycombinator.com/item?id=4495305, and the other part had a major thread in 2011: https://news.ycombinator.com/item?id=3055154 https://news.ycombinator.com/item?id=3055154.
- SixSigma 10y agoYou can't flamewar with Uriel any more. He suicided. Sodium pentothal bought online from China. Every time my Skype starts is has "Hey Uriel, don't drink the wrong drink" in my recent messages. That crazy bastard.
- deleted 10y ago[deleted]
- deleted 10y ago[deleted]
- partycoder 10y agoJavaScript in Web browsers has a lot of sandboxing (i.e: babyproofing). Node on the other side doesn't. If you are an experienced developer, chances are you won't do something lousy like coding by trial and error and playing with concepts you don't understand and copying and pasting from StackOverflow. If you follow the golden rule of not touching anything you don't understand, you should be in a safe spot. But that's not the culture in the node community. The node community is all about sharing lousy snippets of code without error handling, without input validation, and without any regard for any non-functional requirement in poorly written blogs and npm. A community of excessive optimism and irrational risk taking. Floating point numbers, for instance. Every number in JavaScript is a floating point number, and 99% of node developers don't understand a basic thing like how to compare 2 floating point numbers. And that's just the basics... let's not even discuss concurrency, parallelism, how to deal with files, memory, I/O...
- wwalser 10y agoIs this advocacy for safer development environments or just mud slinging at the Node community? You called a critical security layer that protects literally billions of users every day "babyproofing". No only Javascript but most features of web browsers are sandboxed as well, is that babyproofing or smart(prudent?) design? Infantilizing programming communities. I'm ready to move on from this drivel. People make choices based on their contexts and while some large amount of those contexts differ only slightly from my own, I find it impossibly difficult to pass judgement on those who have made different decisions than me.
- partycoder 10y agoI said very clearly that node.js is a serious technology, and so are web browsers. The problem is that the community at a large and companies today have been influenced by a mindset that does work in sandboxed environments but not in actual server-side software.
- supernovae 10y agoThis could be said about everything. BUT, lets be real. Operations people love Node because i can run 100 containers of a node app behind a load balancer. If a single node app dies the orchestration system re-starts it. If developed well you have a reporting/analytics/metrics platform and tracing tool that allows you to capture failures, fix them and deploy new code. I'd wager that for the majority of the world, no matter the language used, most people are implementing patterns/behaviors because that is what they need to do something. Very rarely do people create something / invent something novel thus the level of developer abilities you seem to project don't need to be the standard abilities and that is ok.
- Jemaclus 10y agoDisclaimer: I worked with Node.js full-time for about 14 months, ending about 9 months ago. I'm willing to admit that the following complaints may or may not be out of date, especially with ES6 and newer Node versions. Proceed with grains of salt at the ready. There are a lot of things to like about Node.js, but the primary thing that bothers me about it is the obsession with async. It's a language/framework designed to make pretty much everything async. In the real world, almost everything is synchronous, and only occasionally do you really want async behavior. By that I mean, you almost always want A, B, C, D, E, F, G in that order, and only occasionally would you say that you want async(H,I). But with Node, it's the other way around. You assume things are async, and then specify synchronous behavior. Instead of assuming A; B; C; D; E; F; G;, you wind up with a ton of code like A.then(B).then(C).then(D).then(E).then(F).then(G); ...I know that's a contrived example, and I know you don't really need to do it that way, but so many people do, and it really illustrates the point. In Node.js, you are explicitly synchronous / implicitly async. Most other coding paradigms (including Go) better match what I consider reality, which is that everything is implicitly synchronous, and you specify async behavior when you need it. Basically, I think it's backward. But perhaps like the OP, I just can't wrap my head around it. The NPM stuff... well, I think all ecosystems have their pros and cons. I'm not a huge fan of NPM, but it does the job for the most part, and I'm curious as to how people would actually improve it, rather than just complain about it all the time. I don't really have any good ideas (knowing nothing about how package management actually works under the hood).
- zaidf 10y agoI think the idea of having a powerful scripting language based on JS is a godsend in many ways. But like you, I also feel that async is a bad default for a language that has such widespread use. I love being able to use one syntax to write 95% of my code(instead of having to switch between JS / python / php etc.) but some of NodeJS's programming and ecosystem realities are annoying to say the least.
- jomamaxx 10y agoYour comments about the annoyingness of async are real. BUT Just because you want to do ABCDE does not mean it's feasible. You can access a file, read it, compute something, depending on that access another file, read it, write something via Http Post somewhere else. BUT the nature of i/o is such that the problem is 'intrinsic' - it's not a 'node.js' problem so much. Of course you know that you can do everything syncrhonously if you want, but then you get hangups and what not waiting for underlying resources, networking calls etc.. The nature of a distributed system is inherently async, and so we have to live with it. That said - maybe you have some examples of where async definitely should not be used? The other huge problem with Node.js is the vast, crazy expansion of tiny libraries, supported by ghosts, that change all the time. A simple lib can depend on a dozen others, with varying versions, everything changes almost daily. A small change somewhere can really jam things up. This is by far my #1 concern, although it can kind of be avoided if you're careful.
- supergetting 10y agoI embrace change in life in general, such a view translates over to the complex ecosystems in technologies, I embrace and accept the complexity of every single technology, honestly it is quite amazing. It's good that we try abstracting away many things and make them more simple and less complex, but sometimes inevitably leads to more complexity and more shit, and I like it and it's fun to be part of such journey!
- wyqydsyq 10y agoAll the points in the first (Uriel) rant are attacking JavaScript itself, and most if not all those points are remedied by using ES2015 and FRP. All the points in the second (Ryan) rant are attacking bloated/poorly-scoped software and abstractions, and none of the points (except mentioning $NODE_PATH) have any relevance at all to Node.js. So really none of this is relevant to Node.js (or JavaScript) being inherently bad, it's just pointing out that people can use it for bad things, which is no different to any other language or runtime.
- a_j_s 10y agoyou are absolutely right this is a click bait post that should be down-voted.
- deleted 10y ago[deleted]
- ilostmykeys 10y agoHaters will be hatin'
- arisAlexis 10y agoThis whole thread would not exist when async await gets traction
- Rapzid 10y agoThere will be new threads about how the streams and other standard classes dealing with IO need to be rewritten/expanded to work well with async. I've been using async/await for about a year now(in node.js, much longer in C#) and took to wrapping them when needed; you find various levels of difficulty depending on how much eventing is involved. All the information hidden away in non-public properties/api's doesn't help. MS had to go through and expand out all their stuff with Async methods. I wonder how long the node.js maintainers will take.. Async/await, let, and TypeScript have made node.js bearable for me but, TBH, I'd rather be working with Go or C# more. Owell, right tool for the job and all which has a temporal component as well.
- arisAlexis 10y agoYou don't need o wrap anything promise based and curretly all major libs deliver promises
- elmigranto 10y agoHe talks about events.
- moonshinefe 10y ago"processes orchestrated with C. It’s a beautiful idea." That's all well and good until programmers don't know how to manually manage their memory properly or use pointers and it creates massive security holes and bugs in general. Which is unfortunately very, very often. Apparently this guy disagrees and that's fine, but in my experience he's wrong to bash complexity and praise C. I've read many large C projects' code, and it's about as complicated / messy as it gets. Some good points in the article other than that.
- jtolmar 10y agoSo what do people use as a server these days? All I want is to annotate some function calls with paths and have something handle http requests and mangle the input and output into json for me. Preferably in a boring safe language. Preferably in Java, the boringest safest language. If I have to call a method on a provided object instead of returning in the name of async, great, that's fine too.
- moonshinefe 10y agoif it's not performance critical, I'd go with Python. If you need max performance, I guess Java or Go or something along those lines, though caching and other techniques can soften the blow of using a slower language quite a bit.
- robin_reala 10y agoSounds like a job for Dropwizard. http://www.dropwizard.io/ http://www.dropwizard.io/
- angryasian 10y agoTake a look at spring boot - http://projects.spring.io/spring-boot/ http://projects.spring.io/spring-boot/ its incredibly easy these days to do what you're suggesting in Java
- EtienneK 10y agoI second this. Spring Boot is the greatest thing to happen to Java in a long time... Well, that and lambdas...
- ganeshkrishnan 10y agoAnd if you want to add icing to the cake I suggest Jhipster. It has made my life considerably easy with it's angular JS support and spring boot /JSON/ API support. I could create an e-commerce website http://www.haggell.com http://www.haggell.com in a space of month using jhipster & angular.
- regularfry 10y ago
- lootsauce 10y agoThere is an easy sense of superiority that comes with derision of "X" and the authoritative sounding romanticization of idealized "Y" seemingly adds weight to the argument. Clearly these "Y" people are smarter and better than all those "X" people. Look at all this horrible code! So sad that all these people are not as smart as me. Look at this horrible language! So sad the people that created it are not as intelligent as me! Really? There is no more "problem" with Node.js than there is a "problem" with any other platform. There is no more problem with JavaScript/ES-(name your flavor) than there is with any programming language. Different languages are different. Different platforms are different. Of course every system has its own problems. Sometimes people who appreciate them call these "tradeoffs" or the superior types call them idiotic. The cliche´ of hacker news haters is really really really getting old. So here are some things that are actually good. As much of a pile of hot steaming code as it is, Babel as an idea (AKA transpiling one language to another) is pretty cool. Of course you can do this in other places but its featuring prominently in the JS community leading to an interesting result. The language and its features become configurable, easy to adapt and change and evolve over time and suit to your liking. This is interesting! Finally as opposed to what others may have said about the community being childish I have found the opposite. I find it to be very welcoming and supportive, friendly and honestly creative. Of course there are lots of negatives, lots of horrible code, lots of mistakes happening. But what is missed in all of this? Theres A LOT of stuff happening that is good even great! It's beautiful chaos! So go on hating, but I see lots of great stuff out there. As one great systems and iOS developer told me the other day "Have you tried Express? Its awesome!" HA yeah. But he just tried it, and loves it! Oh but look at that callback YUCK! Cmon
- murbard2 10y agoSo for example, the Javascript rules are no more problematic than the casting rules in other languages, they're just different?
- lootsauce 10y agoNo, like my cat likes to snuggle but sheds and my dog likes to play but poops too much. Either way they both deserve a bowl of water and some food at the end of the day. You can get all pedantic and say cats are better or dogs are better but guess what. I don't care, I just like my pets.
- Wei-1 10y agocannot agree more, but we still use it.
- aaronbrethorst 10y agoQuasi-related, one of my favorite programming language essays of all time: https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/ https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/ From what I've observed, I feel like Node is where hipsters who decided that PHP was "icky" ended up.
- rv11 10y agoI see a lot of desktop apps made from electron/CEF using Node. examples are Brackets and Steam.
- spion 10y agoThe pot is calling the kettle black. Its always funny to read something like this coming from proponents of Go. Now thats a language that threatens to single-handedly bring us back 30 years in the past. A typed language invented in 2009 lacking generics and algebraic data types, and being proud of it (or at least its users being proud) - thats pretty much at the exact same level as JS "reinventing" callback-based async programming in 2009. And its users were similarly proud of this in 2010-2011. At least Brendan Eich is modest enough to apologise for JavaScript's flaws and push as much as possible for fixes without backward compatibility breakage of the web.
- geodel 10y agoHow can one language not even in top 10 bring us back 30 years? Has it been made compulsory to be used by developers?
- pswilson14 10y agoNot OP, and I don't have an opinion on Go, but I think that's why he used the words "threatens to".
- spion 10y agoPeople are already asking for the (err, res) crap in other languages too on Twitter.
- tim9009 10y ago"The only thing that matters in software is the experience of the user." "if you add unnecessary hierarchies in your code directories, if you are doing anything beyond just solving the problem - you don’t understand how fucked the whole thing is." Oh really? So making the code easily maintainable and easy to understand is just a waste of time? Comments like that makes it hard to take the rest of what he says seriously.
- tim9009 10y ago"The only thing that matters in software is the experience of the user." "if you add unnecessary hierarchies in your code directories, if you are doing anything beyond just solving the problem - you don’t understand how fucked the whole thing is." Oh really? So making the code easily maintainable and easy to comprehend is just a waste of time and simply ads complexity? Comments like that makes this hard to take seriously.
- ComodoHacker 10y agoTL;DR: >I hate almost all software.
- greendestiny_re 10y agoI'd just like to point out the linguistic paradox of the "one of the worst" syntagm, as only one thing can be the worst, and "one of" implies a multitude of such things; if 20 things are the worst, then none of them are. In short, this is a lazy way for the writer to express his opinion but label it as a fact.
- jondubois 10y agoI don't see anything wrong with Node's approach to concurrency. It uses IPC which is much more scalable than threads and mutexes. Also, you don't have to use callbacks anymore, now we have Promises and there are tons of libraries that allow you to do reactive programming so you can just wire-up streams of data together in complex sequences. This article is just inflammatory and illogical. I think Node.js is one of the best backend engines which was ever created - And I've programmed in everything including AVR Assembly Python, PHP, C#, C/C++, Java and many others. I like Node.js the most. And yes, you're right, the Node.js community isn't a 'proud' community - We're more interested in constantly improving than sitting there being satisfied with ourselves whilst bashing other tools. There is no perfect tool/stack; they all have pros and cons. It's all about personal preferences.
- wjagodfrey 10y agoWell said. To everyone responding positively to this article, enjoy your confirmation bias. Have a side of emotional reasoning while you're at it.
- premium-concern 10y agoSometimes it's hard to tell satire from reality, but you gave it away in the end. :-)
- signa11 10y ago> I don't see anything wrong with Node's approach to concurrency. to me, erlang's model seems to be the best one that is around. without a runtime scheduler, message boxes + selective receive etc., i don't really think it is possible to do justice to the whole csp thingy. you can have approximations to it, but that doesn't go very far. for example, in erlang, i can start processes etc. and have them run essentially while(1) { } and nothing really bad happens to other concurrently running threads.
- coldtea 10y agoWhat those repeating "async is good" don't seem to get is that we have had better ways to do async than what Node.js offers for decades. Better as in, all of: faster, easier to reason about, better implemented, more robust. Erlang is but one example.
- narendraj9 10y agoCannot access the site.
- andrewstuart 10y agoI rather like JavaScript. ES2015 anyway.
- yAnonymous 10y agoYeah. I hate all these great text editors and other cross-platform software that Node brought about.
- kabes 10y agoThe article is not very relevant in 2016. Much of the arguments are not valid anymore.
- deleted 10y ago[deleted]
- everydaypanos 10y agoNode.js solves the problem of "live webpages" w/ Websockets and Polling and chat apps and notifications etcetc. And that counts. A lot.
- 6nf 10y ago> Websockets and Polling Those have nothing to do with Node, you can implement them with just about any server-side stack.
- myf01d 10y agoI am interested. What is Node.js people opinions about Django in 2016? I am a newbie and I chose Django for a somewhat serious personal project. Is it really bad to use django for a new project in 2016?
- daishinlabs 10y agoNo. You got it right Go ahead!
- OOPMan 10y agoNothing wrong with Django, it's a perfectly decent web framework. Not every system requires the async paradigm of Node in order to be useful. For those that do, the ecosystem is more diverse than just Node anyway. On the Python side, for example, you can use Crossbar or Django-Channels. Personally, I prefer the former but the latter is also usable.
- Jean-Philipe 10y agoUriel didn't quite explain why PHP is any better than nodejs. I'd be even interested to hear!
- SixSigma 10y agoYou're too late. He suicided.
- leonroy 10y agoI've been a software dev for 10 years. When I started I saw the transition from Perl to PHP and a lot of snobbishness from the former towards the latter. Seeing the changing of the guard in web languages was pretty instructional and it's something I see again and again. I think basic CompSci courses should really have a course or two on managing software projects and handling the problems of what framework do I use to build my new software app? Because fundamental language or framework decisions have both a technical and a business component and even as a front line programmer it helps to be aware of both. Node.js is a great environment for getting a server side app going fast and it has very good tooling thanks to the rest of the JS community with additions like npm, gulp, bower, express etc. There's obvious benefit in having shareable libraries between client and server side and most importantly (to software companies) hiring coders who can work with it is far, far easier than say finding that rarest of unicorns - an experienced Haskell developer. If (and it's a damn big if) you outgrow Node.js you're doing well. Then (and only then) look at the alternatives like Play Framework, Spring Boot, Vert.x or whatever else floats your boat. Rants can be useful in giving a kick up the asses of the relevant community to go address certain bug bears. This rant though is so damn generic it reminds me of those Perl developers at college pouring cold water over the idea of using PHP because they felt threatened by it.
- ido 10y agoI think basic CompSci courses should really have a course or two on managing software projects and handling the problems of what framework do I use to build my new software app The problem (if it's a problem, depends on who's asking) is that undergrad CS courses mainly train you to be a CS graduate student (which in turn train you to be a CS academic), but most students choose to major in CS because they want to become professional programmers (aka Software Engineers). I've done both bachelor and master level CS studies and job-preparation-wise would probably have gotten as much (or more) from a 1-1.5 years (2-3 semesters) vocational training than I did from 8 years of university. Probably the most apparent perk my studies have gotten me career-wise was being invited to interviews at major tech companies like google and amazon.
- jalanb 10y ago
- phazelift 10y agoUnbelievable, so many up votes for this complete idiot statement..
- YeGoblynQueenne 10y agoSo, this is totally an ad hominem but the OP webpage has a post category titled "Political Correctness" [1] with one post titled "Claims that sexisim drives girls away from Computer Science are feminist bullshit." [2] and one link to an external site titled "Sex Differences in Mathematical Aptitude - By La Griffe du Lion." (a.k.a. "Lion's Claw") [3] starting off with this bit, styled like a research paper abstract (you know, to make it look seintifikal): Mathematics is a man's game. A gender gap appears early in life, blossoms with the onset of puberty and reaches full bloom by mid-adolescence. It indelibly shapes women's prospects for doing significant mathematics. In this account of cognitive sex differences, Prodigy shows how sex-differentiated ability in 15 year-olds accounts for the exiguous female representation at the highest levels of mathematical research. A female Fields Medalist is predicted to surface once every 103 years. I stress again that this is essentially an ad homimem: I'm absolutely flagging up this dude as a sexist baboon with brains the size of a small, frozen pea. And because I have much better things to do with my poor feminine brain (say, finish off my MSc dissertation, on a novel grammar induction algorithm) I'm not reading a single word of the OP. ________________________________ [1] http://harmful.cat-v.org/political-correctness/ http://harmful.cat-v.org/political-correctness/ [2] http://harmful.cat-v.org/political-correctness/girls-in-CS http://harmful.cat-v.org/political-correctness/girls-in-CS [3] http://www.lagriffedulion.f2s.com/math.htm http://www.lagriffedulion.f2s.com/math.htm
- deleted 10y ago[deleted]
- gens 10y ago..I was going to write my usual long speech about how all humans are basically the same. but you know what ? Nah. There will always be narrow minded people. And to battle narrow-mindness one should read books (good books[0], that is). If dismissing someones opinion not because of the opinion itself but because the author of that opinion linked in an unrelated opinion piece to a completely different persons opinion (edit: that, by reading it, may even be a satire) makes your boat float, then we have nothing to talk about really. Have fun in your academic life. (sincerely!) [0]http://lkml.iu.edu/hypermail/linux/kernel/0707.2/4230.html http://lkml.iu.edu/hypermail/linux/kernel/0707.2/4230.html edit2: I'm sorry if i offended you. I don't know anything about you really. I was just going a bit into the extreme to make my point.
- neelkadia 10y agoCan you make it good?
- cdevs 10y agoI used "callbacks" when needed in objective-C in my app days and got sh#t done just fine. I think the best thing to come from node is the ability for a younger crowd to jump into proton/electron desktop apps without needing to get into sdl, qt, or some platform specific language like objective c or the .net C# whatever family. Nose might not be the finally language to take us to that area but it's a start and a ton of awesome open source apps came out of the scene quickly.
- pjmlp 10y agoI think that bloated piece of software is one of the worst things to happen.
- tflinton 10y agoI've done a fair amount of messing around with javascript. 1. Recompiled webkit into javascript using emscripten/asm.js (webkit.js) 2. Created a desktop version of node (tint2) using FFI calls for OSX/Windows 3. Reconstructed much of the oracle o5login/tns/tti protocol for giggles (and if you want to see a very head scratching way of packing 64 bit signed ints, look no further than 11g). What I can say is it isn't perfect. But it has one gigantic advantage is you don't need to build or compile to run, but still get nearly the same performance from compile time languages. It's a near perfect prototyping language, and for most peoples use (e.g., 99% of crud/general business humdrum logic) it's perfectly fine. Just stay away from relying on too many npm modules.
- k__ 10y agoWhat I find interesting is, that everyone has rather hard feelings for any language but Python. There seem only 2 things people complain about Python, performance and the two major versions out there. Overall I have the feeling most devs thing it's pretty okay.
- detaro 10y agoPackage management is another typical complaint. Admittedly it's a complaint in nearly every language that has packaging tools.
- tgarma1234 10y agoWell I am by no means a great computer programmer or anything so I can certain accept other people saying node is crap but as someone who has used node my reasoning was simple: if you are going to use javascript in the browser and pretty much everything about the "app" depends on what happens in the browser then why use some other language on the server for models and controllers with javascript in the views? Why not just make it javascript all the way down? Sure, smarter people than me might know why I shouldn't use javascript for everything but for me I do not find it useful to try to figure out how to do so much work in Rails or Django AND THEN ALSO end up using javascript in the views every time anyway. I would rather skip using Rails or Django and just get to the fun part of figuring out what happens next when this button is clicked on the website. I don't think I am alone in that. Rails and Django were a means to an end but they set the bar too high in terms of "programming" and require a lot of programming knowledge that I don't actually need to know to do what I want to do now with node. Sure, my code might suck but unless you are working in some super professional environment with highly skilled managers, pretty much everyone's code sucks. It's about getting the functionality you want with the least amount of effort. Node makes that possible.
- davidgrenier 10y agoYou do everything you can to use something other than JavaScript in the browser. The list of good languages that targets the browser is long, the last of bad languages better than javascript that targets the browser is even longer. I personally used WebSharper and it's excellent. All these sophisticated frameworks (thinking Angular foremost) have nothing on WebSharper.
- youdontknowtho 10y agoThis kind of thing gets really old. From reading HN you would think that Java is the worst thing ever... OO is the worst thing ever... Microsoft is without a doubt the worst thing ever... systemd is the worst thing ever... C++ is the worst thing ever... JavaScript is the worst thing ever... This one feature of OS X is the worst thing ever... Paying for software is the worst thing ever... Not being paranoid is the worst thing ever... Redhat is the worst thing ever... Outrage is boring. It's everywhere and whatever weird random thing you are on about isn't anymore novel or interesting than anyone else and their weird little random thing. It's like everyone turned into Dennis Miller and then started to suck just like Dennis Miller. Amirite? I'm rite? rite? What's with all these rants these days? its like two guys dancing the lindy hop in a zeppelin, I mean come on folks...
- nilved 10y agoI try to understand why people would write JavaScript but I just can't. The only explanation to me is that they're not aware of what they're missing out on, or the deficiencies of their own platform, in a Dunning-Kruger sort of way. I would be interested in hearing from some JavaScript developers about why they use JavaScript, but I have probably heard and refuted it before. Especially after Ryan Dahl disavowed Node, I think it's time to reconsider your viewpoint.
- punnerud 10y agoNASA is using Node.js for its Mission Control Framework https://nasa.github.io/openmct/ https://nasa.github.io/openmct/ https://github.com/nasa/openmct https://github.com/nasa/openmct
- 1_listerine_pls 10y agoIt's a Non-technical argument in a technical discussion. Is a framework necessarily better/good because it was picked by the SE team at a large company?
- derptron 10y agoFacebook used to use PHP. That doesn't mean PHP isn't a pile of shit.
- lllorddino 10y ago> better alternatives around with much more sound models and environments, Erlang and Go Node.js makes it extremely fast to build robust and fully featured web apps quickly. I'm using Go currently for the backend and it's a pain since everything has to be written from scratch. I still enjoy it since the language is simple.
- mcs_ 10y ago》There will come a point where the accumulated complexity of our existing systems is greater than the complexity of creating a new one. When that happens all of this shit will be trashed. I think it applies to bank system, politics, and more in general to anything that can be improved and where there are enough money to think about re-design. At that point yes, another life cycle will starts.
- progrocks9 10y agoNodeJS works great as a simple web or network container, if you're trying to create a complex enterprise app in Node, basically you're doing it wrong. Simply it's difficult to design complex nested logic or algorithms in a clean manner. It's possible but it's harder than other languages.
- agentultra 10y agoThe worst thing is a gross exaggeration. I've been guilty of these at times. It seems common. You have to be a very passionate person to care deeply enough to master programming. These are infuriating machines operating in the domain of discrete maths... one error and the entire building comes down. That being said sometimes, when there's no one else you can kvetch with, a good rant is just what you need. Computers are stupid. Programming is horrible. Everything is terrible. But Node.js is hardly the worst thing. Some perspective is required.
- diegoperini 10y agoFacts are nouns, adjectives are subjective. A subjective analysis is hard to trust. I hate Java, because I choose to do so. Java being a bad language cannot be proven by my personal opinion. People do amazing things with it, Minecraft was initially Java, Android apps run on JVM etc etc. This article has more than 10 adjectives (many have adverbs attached to them or written like "... much more sane and reasonable language like Python ...") in its first five sentences. Thanks for the effort but no, I cannot trust any of it.
- klodolph 10y agoThat's a weird metric. "Java is an abomination" uses nouns but is entirely subjective, "Java is class-based and garbage-collected" uses adjectives and is objectively true.
- diegoperini 10y agoI'd try to save my argument here but I know I'll fail hard. Let's try :) "Abomination" implies disgust, so your example can be paraphrased as "Java is disgusting.". To fail harder, let's paraphrase further. "Java programs are built with classes and collect their garbage." At least I've tried. My own comment actually has adjectives too (like "subjective") but this is getting too meta.
- diegoperini 10y agoOne more thing; f word in critical posts about computer science related stuff is a bad abstraction.
- api 10y agoMeh. It works. Npm is okay if you exercise quality control over what packages you use and keep dependencies down. The language is decently productive for scripting and everyone knows it so it's easy to find maintainers. It performs well and can be multithreaded just fine by running many concurrent node workers and using a good database and cache. Go may be better but has a less rich ecosystem of turn key solutions and easy integrations. Java is a decent language but has an outdated ecosystem. .NET going OSS is interesting. Ultimately what you do with languages and tools is more important than which ones you use.
- annasaru 10y agoJ2EE is up there.. We have a generation of corporate Java programmers who love boilerplate code and obfuscation. High-School teachers inflicting Java on teens - cringe-worthy. Many public schools only offered Java if you elected programming/CS (in High School). Only recently has Python made inroads.
- imagist 10y agoIt's telling that none of the posts defending Node.js are talking about it's technical merits. They're all saying: 1. Attacks on people--you're being too negative, you're saying this to feel superior. 2. Choosing Node.js is a tradeoff! We can't really say what you get in exchange for using this crappy ecosystem, but "tradeoff" sounds good even if you're trading using a reasonable ecosystem for nothing. If you really think Node.js isn't a flaming pile of crap, I challenge you to come up with something it does that isn't done far better in another ecosystem.
- geofft 10y ago> I challenge you to come up with something it does that isn't done far better in another ecosystem. A single, standard event loop that literally every library in the ecosystem uses so you don't have to worry about it. The other options are compiled languages (Windows message pump, Qt or GTK+ event loop, etc.), which aren't what people seem to want for Node's use case, or things like Twisted. For all of those options other than maybe Windows, you don't get to assume that the entire ecosystem speaks the same event loop protocol. And I don't think any of these options do it far better than Node does. Twisted is pretty good, probably a little better, but Node is just fine too. Note that I am not a Node.js programmer. I can kind of work with existing apps in Node because I can kind of write JS sometimes (I'm really more of a C person). I just know what other technologies are good at.
- PeCaN 10y ago> A single, standard event loop that literally every library in the ecosystem uses so you don't have to worry about it. Tcl? Erlang/OTP?
- imagist 10y ago> A single, standard event loop that literally every library in the ecosystem uses so you don't have to worry about it. Using an event loop with all the other threading models available out there is like bringing a knife to a gunfight. I could maybe argue that JavaScript's event loop isn't as good as other event loops, but while actor models exist, I'm not sure why we'd even talk about event loops.
- clifanatic 10y agoWell... all the things like DBus and /usr/lib and Boost and ioctls and SMF and signals and volatile variables and prototypal inheritance and C99FEATURES_ and dpkg and autoconf that he's complaining about were originally conceived as a way to simplify something that their respective authors considered too complex in the first place. I'm not holding my breath that the next attempt to simplify all of those doesn't just add yet more complexity. On the plus side, job security.
- _c_ 10y agoFrom Rob Pike quote at the end, after the Ryan Dahl quote: "... the UNIX/POSIX/Linux systems of today are messier, clumsier and more complex than the systems the original UNIX was designed to replace." "Messier, clumsier and more complex" are adjectives that could describe almost all of today's software vis a vis software from the 1970's. This is not a criticism of today's software it is just the evolution (or devolution) as it happened, an objective observation. By and large, programmers do not attempt to make software more clean, more efficient or less complex. Most do not spen all their time cleaning up messy code, fixing bugs, or sacraficing inefficiency at the expense of usability or abundance of "features". And almost none spend time removing code and reducing complexity. They do the opposite: add features, pursue "ease of use" at the expense of common sense and incessantly generate and commit code believing that any decline in commits or "software updates" signals a project is "dead", not "modern" and probably in need of a "replacement". Again, I'm not critiquing this, I am just stating the facts. This is what they do. Not sure about Pike, but the reason I think some older software is higher quality than most newer software is not because it was or is high quality in an objective sense. It's because today's software is so low in quality and in too many cases worse than yesterday's. Indeed, it's "messier, clumsier and more complex." In an objective sense, 1970's UNIX is nothing to celebrate. But compared to the then-alternatives, what came afterwards, and what we use today, it can be held in high regard. It's only good in a relative sense. Everything else was and still is so bad. (Why is anyone's guess.) Avoiding the hassles Dahl alludes to[1] brings me a certain feeling of satisfaction. My language of choice is Bourne shell. And if I am just working with text, such as reading and writing, I do not use a graphics layer - no X11. The question is: Does Pike's comment apply to Plan 9? 1. Not to mention avoiding the needless complexity and obscurity of Microsoft Windows.
- JDiculous 10y agoAnybody can criticize a language or platform, but it doesn't mean much if there aren't any better alternatives. This article presents an extreme conclusion without much supporting evidence, so it's pretty pathetic that this made the front page. Nobody even uses callbacks anymore now that we have Promise and async/await. Yes, Javascript isn't the best language (though ES6 improves tremendously on ES5). But right now it's the only language you can use in the browser (aside from languages like Clojurescript that compile to Javascript). The biggest advantage of Node.js is that you can reuse the same code on the client and server, and thus it's ideal for creating universal single-page web apps. Being able to reuse the same code on the client and server is a massive advantage that can't be understated. Also, Node.js with Nginx is more scalable out of the box than Ruby on Rails, Python/Django, PHP, etc. Hell it's comparable to Java, which is incredible for a dynamic language. The difference is, you can write a Node.js web application 10x faster than the equivalent application in Java, and with a drastically smaller codebase (less code = less code to maintain). These days developer time is the biggest cost. These rants come off as coming from either (1) back-end developers who never touch UI code or anything on the client-side (not where Node.js thrives) (2) armchair commentators who don't actually have to get shit done in terms of building and deploying web apps on deadlines, and thus have the luxury of criticizing everything without presenting realistic alternatives. > "There are only two kinds of languages: the ones people complain about and the ones nobody uses." -Bjarne Stroustrup
- funksta 10y ago> Nobody even uses callbacks anymore now that we have Promise and async/await. Sadly this is not true (yet)
- ewzimm 10y agoI agree with most of your saying, but the second rant is by Ryan Dahl, creator of Node.js. Often these rants come from people who are very competent and know what they're talking about, but anybody can get burned out by working too much, and the annoyances of flaws can become overwhelming. It's worth remembering that we can always iterate and improve on what we have, even if it's good enough, if nothing else than for the sanity of the people who have to work on cleaning it up later.
- Roboprog 10y agoAsync I/O - CON: I hate having to set up callbacks (even with promise syntactic sugar), whether I need them or not. But of course I do need them when I am coding a U/I. PRO: the "promise-all" trick is pretty useful if you have several queries that all need to be completed before you can continue with their results. I have some Java code that might benefit from this since it does several queries to generate a PDF. (then again, caching might make this moot - YMMV)
- soupdujour 10y agoI don't understand why people think node doesn't scale or that you need to use something else when it's time to "get serious". I can't get into specifics, but I recently worked on an app for a rather large company that had 10s of millions of daily users. The app written in node needed 3x fewer cpus than a java app running in the same system and they were performing similar tasks with almost identical usage. The team maintaining the node app was also 4x smaller than the team maintaining the java app. The main difference was that the node app was thoughtfully architected and written and the java app was not. It didn't have anything to do with language or tooling. It had to do with good software engineering.
- Anagmate 10y agoI feel like a large part of the negativity around Node.js comes from the callback hell and almost everything being async. Solution to these two problems (an ingenious one I think) is async/await (and there is an awesome polyfill on npm) - if you want, you can enclose your whole code in one async block and effectively make everything synchronous. Or you use it to its full potential and remain synchronous in all parts of the code that need it while retaining the benefits of async (other parts of code can run while the current one is waiting for a result. The only caveat I've encourtered (a manageable one, at least for me) is that you must keep in mind that the underlying code IS async, so you can only guarantee synchronous behaviour in the single asynced block od code - so sometimes, race conditions could happen between some parts of your program, but with proper scoping (and ideally, using pure functions), you can avoid it all together.