4 ms·
I am managing (as a tech lead) a couple of node projects, ranging from small apps to projects being developed for more than a year. And although I always liked
by cygned 10y ago
I am managing (as a tech lead) a couple of node projects, ranging from small apps to projects being developed for more than a year. And although I always liked node and although I kinda live in JavaScript every day, I am looking forward to replacing the backend in new projects with something different (going to use Clojure).
The reason is that the whole JavaScript eco system can be extremely frustrating. Here a couple of examples:
- If you install dependencies with npm there's a good chance you have minor version changes - which would be okay according to semver, but we have two challenges there: (a) even minor updates can introduce bugs and (b) a lot of JavaScript developers don't really care about breaking changes that much.
- Documentation is huge problem. Even good libraries/frameworks often have an awful documentation and I often have to spend time in third party code finding out how things should be used
- Many libraries get abandoned because the developers moved on. That's very sad. Especially, if there are bug reports pending, open pull requests from volunteers and so on.
Maybe other eco systems have the same challenges, but that's my current feeling about node.