3 ms·
I think a lot of the frustration comes not from the new languages/frameworks themselves, but all the endlessly re-invented support tools that surround them. Fo
by danenania 8y ago
I think a lot of the frustration comes not from the new languages/frameworks themselves, but all the endlessly re-invented support tools that surround them.
For example, learning React itself is great because you can pretty quickly see how it cleans up your UI layer. It doesn't take that long and adds real value to your projects.
Oh, but now you need to learn all the corner-cases of NPM, and now you need a new test framework, and now you need to figure out the incantations to get webpack x.y.z outputting just the right way. Oops now hot-reloading is broken. And the chrome inspector is lagging for some reason.
None of these are interesting or fun problems to solve, but they are a pretty substantial part of getting any new technology into production.
- kentm 8y agoOur profession consistently ignores operation and maintenance in favor of building a new thing, despite the former being at least as important. How many people post negatively about Java in terms of productivity and cite boilerplate as a productivity-killer, despite the massive advantages a JVM stack brings?
- timdavila 8y agoYep, this is why I'm much more inclined to go with something I know on the front end. I'm not against learning a new framework, but fighting the tooling is one of the more frustrating things.