3 ms·
I would also add something along the lines of "building big webapps". Large frontend codebases used to be scary Lovecraftian horror where things were only touch
by Etheryte 5y ago
I would also add something along the lines of "building big webapps". Large frontend codebases used to be scary Lovecraftian horror where things were only touched out of utmost necessity. Runtime errors for weird corner cases. Dangling dependencies that no one could figure out whether they're safe to update/remove or not. Refactoring was both an art and an arcane incantation at the same time. Modern tooling and best practices have made most if not all of these problems nearly non-existent, and I'm grateful for it.
- freedomben 5y agoOh man, this brings back nightmares of upgrading jQuery, and third party components that were copy/pasted into the codebase and modified/customized. Large frontend codebases are indeed miles ahead of where they used to be.
- earthboundkid 5y agoThe step backwards is that before, you couldn’t upgrade jQuery because the CDN script tag was on thirteen different partials, and you weren’t sure which were still in use, and now you can’t upgrade React because it depends on v4.3.2 of chalk-babel-duster-pack-plugin and that’s insecure but it has a breaking change in v5 you don’t know how to fix, so you’re just waiting for a total rewrite of the app to pull out CRA and replace it with Vite or some such.
- nicoburns 5y agoOr you can avoid CRA in the first place. CRA is frankly a hot mess. But React itself, and for the most part even Webpack are quite reasonable.
- prashaantt 5y agoWhat are your issues with CRA?
- gdulli 5y agoThere's some kind of law of conservation of complexity. Often we don't solve it, we just move it around or repackage it.
- salawat 5y agoIt's called the Waterbed Theory. https://en.m.wikipedia.org/wiki/Waterbed_theory https://en.m.wikipedia.org/wiki/Waterbed_theory