i'll admit it. i'm actually rather impressed by the work going into node.js. There are new libraries and methodologies rolling out every week or so that address some basic shortcoming in a clever and interesting way.
Granted, there's no way in hell that i'd use only it to build a large scale, maintainable system, but i'm still impressed.
There, that should help, shouldn't it?
Allow me to explain using something that's imposing itself on me. Recently, my wife (and to a slightly lesser extent, i) decided to have our bathrooms redone. i live in a 50+ year old ranch that was originally meant to be a "starter" home. That means it was built reasonably quicky and cheaply following one of four floorplans that probably took some architectural student a weekend to craft. There are some shortcomings that we've been addressing, but by and large, we're still very happy with the house.
It also means that we've hired construction folks to come in and work their various crafts in order to make an attractive, usable set of features that will last at least another 50 years without the same incidents i've already repaired.
In order to perform those destruction/construction tasks, they've brought in a number of tools. Some tools have served multiple purposes (like the impact drill doubles as a screwdriver and socket driver), others are fairly tightly constrained (like the tile cutter which only wet cuts tile). There has been some duplication of tools (hand saws vs. sawsall), and some tools were used in a somewhat disposable way. The project could have used just one set of tools and it might have worked, but somehow i don't believe it would have been terribly efficient to use a Dremel for everything.
All of these tools can do more than that. Some folks have built incredibly complex solutions based off of using just one of these tools and other folks hate them for it. In practice.
i write code to solve problems. There are some that write code to answer challenges, and good for them. i try to keep up with the challenge folks because they may discover a new approach that works better than what i may know of, but generally, they don't. i'd like to think that occasionally the challenge folks might be interested in the "problem" side, but i know better than to demand that.
A good engineer knows what to do to keep an engine running. A good designer knows how to make something new. Both have their places, but know which place you feel most compelled by, and which one will get you paid.