4 ms·
"Excitement and enthusiasm for something new" was left off that list for a very good reason: it's a terrible reason to pick a technology like node (or anything
by javajosh 15y ago
"Excitement and enthusiasm for something new" was left off that list for a very good reason: it's a terrible reason to pick a technology like node (or anything else).
In fact, I'd go so far as to say that enthusiasm for mere new-ness is one of the more pernicious, counter-productive parts of modern hacker culture. Rich Hickey implied this at his RailsConf keynote when he talked about how great we are at judging benefits, but terrible at judging trade-offs. Here's a man who's certainly not afraid of newness itself (I mean, he single-handedly released a new JVM hosted LISP) but I think he has his head in the right place about the cost of new, and what something must provide to justify that cost.
For example, it makes absolutely no sense to use Node and then layer on top of it a web framework that is an isomorphism from some other environment.
Last but not least, I think the key reason we have different perspectives is age. Hickey and I are about the same age. I assert that anyone who trumpets the inherent value of "new" hasn't been around long enough to understand that there is a never-ending stream of new things and that, as Teddy Sturgeon famously quipped, 90% of everything is crap.
The real market for technology adoption should fueled by demand for simplicity, rather than demand new-ness (something else Hickey strongly implied in his talk).
- DanI-S 15y agoI carefully avoided making the statement you've just deconstructed. Nothing in my original post mentions newness. The point I made is that enthusiastic and excited developers are valuable. Developers tend to find learning exciting. They could be interested in learning Rails or Django for the first time, trying out Sinatra when a full Rails app seems overkill, or exploring Node for a small and non-critical part of your architecture. Hell, they might be excited about learning PHP. Allowing people to explore their curiosity brings material benefits. It doesn't have to involve new technology, and I didn't suggest that it does. As an aside: > The real market for technology adoption should fueled by demand for simplicity, rather than demand new-ness I think part of node's mass appeal is that it has introduced an element of simplicity to a generation of developers who have grown up around bloat.
- javajosh 15y ago>I carefully avoided making the statement you've just deconstructed. Perhaps you carefully avoid it, but you also strongly implied it. Consider: >You're lucky enough to live at a time where there are numerous production-ready tools with which to do your job. If you choose a tool that you're excited to explore, with an active and fast-moving ecosystem, your excitement and enthusiasm will make you happier and more likely to do a better job. You're optimizing for programmer excitement. There's a famous graph of programmer excitement curves floating around on the net, with a peak at "new and shiny" stage. >Developers tend to find learning exciting. They could be interested in learning Rails or Django for the first time, trying out Sinatra when a full Rails app seems overkill, or exploring Node for a small and non-critical part of your architecture. Hell, they might be excited about learning PHP. I'm not arguing the truth of what you're saying - it's obviously, painfully true that developers absolutely love trying out the new hotness (sometimes even if it's just new to them). I'm simply asserting that this is bad.
- DanI-S 15y ago> You're optimizing for programmer excitement. There's a famous graph of programmer excitement curves floating around on the net, with a peak at "new and shiny" stage. I at no point said that this should be the overriding factor. I said that the need to consider developers' personal goals is often understated, and is one of many pieces of information worth weighing when making a decision.
- jshen 15y agoIf only a group of more than 5 developers were enthusiastic about the same thing! Your enthusiasm for node is another persons pain. I've got 1 coder enthusiastic about node, another for clojure, and another for scala. Should every project be a different language and ecosystem? What happens when programmers move around in an organization. "I think part of node's mass appeal is that it has introduced an element of simplicity to a generation of developers who have grown up around bloat." Who are you talking about? Right now I'm dealing with a generation of programmers that came up on ruby. Node isn't simpler than sinatra. In fact, we just tried to use node for a "small and non-critical part of your architecture". You know what happened? It took much much longer to finish because it needed to talk to an API that uses digest authentication and node's http library doesn't support that so we had to roll our own.
- zopa 15y agoThis wasn't what I got from Rich Hickey's talk. I understood him to be saying that, while of course you shouldn't use something just because it's new, you should use whatever will make your code simpler, even if there's a learning curve. That to me was the point of his "easy" vs. "simple" dichotomy. Using the tools you happen to be familiar with is doing what's easy for the developer. Hickey argued that you should instead accept a bit of a learning curve if it will simplify your program in the end. Now, I've never used Node, so no idea if it simplifies or complects web programming. (My current projects are in Haskell/Snap; so you can guess how I feel about learning curves.)
- stcredzero 15y agoHere's a man who's certainly not afraid of newness itself (I mean, he single-handedly released a new JVM hosted LISP) Though, I note that at the time, those were two mature and and well pedigreed technologies. I assert that anyone who trumpets the inherent value of "new" hasn't been around long enough to understand that there is a never-ending stream of new things and that, as Teddy Sturgeon famously quipped, 90% of everything is crap. A big reason for that are "pop cultures," which are defined as cultures/sub-cultures whose rate of change far outraces their rate of actual progress. Unfortunately, programming as a whole is one of those things.