|
|
|
|
|
by Tomte
2510 days ago
|
|
Because it's yet another full ecosystem with lots of dependencies where I have zero knowledge and experience. For example, all those packages say "npm install packagename" to install, but it didn't work for me. It seems I have to (sometimes?) do a "npm init" first. No install instructions ever tell you that. I'm sure when you're in the ecosystem, that's a given. For me it's hurdle after hurdle. That's why I named Go and Ruby as examples. The former because you usually get a standalone executable, the latter because I already have that toolchain installed, and I know how to navigate it. Unfortunately, everything in webdev is now node.js. Just look at any CSS framework docs (including Tailwinds, which I really like): it's an endless stream of pre-processors and post-processors, multiplied with all kinds of ES versions, Babel, yarn-or-npm, this build tool or that. It just doesn't end. Rant over. :-) |
|