alt Hacker NewsI would say depends what you're trying to do?
Is NodeJS the simple, solid and rugged way this has been done for a decade now? If not, then it is an innovation.
Second it depends on what your or your teams experience level is.
Have you ever built a serious thing with it and do you have multiple years of experience running and maintaining it? Yes? Then it is probably the boring choice.
Would you be okay with leaving the final product unmaintained for a few years and it would not be a major problem? That may be a factor as well. E.g. a static HTML website needs next to zero maintenance, while a wordpress blog may fall apart every once in a while.
How maintainable would it be if the person who built it leaves? Could someone else pick up the slack right away? Would they need some time to get up to speed? Would it be literally impossible to get up to speed?
How hard is it to get the build system setup if the devs laptop is crushed under a truck? Is it as simple as cloning the project or does it need ritual sacrifice and dark chants and incantations to even get near running?
The boring thing is one that scores all the easy points on these questions.
> Second it depends on what your or your teams experience level is.
+1.
I work in a Skunkworks department inside a larger/older company and we recently decided to stop using Python in the future, the company's language.
Node.js, Go, Rust, C#, etc, all of those are extremely boring for us. They're stable and we get things done in minutes. In Python it's like pulling teeth, with constant API changes and refactors from other teams we're struggling to keep up with. Which one is boring? For us, not Python.
The Python developers naturally disagree and say "there must be something wrong with your team if you can't use Python at the same speed and efficacy as us".