Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
ltlian148723dPreaching to the choir. I'm currently working on internationalization of this react app and I've had to resort to traversing folders and discovering json translation files by regex via require.context().
I put the blame on an expectation for websites to do more than they should. The tools may be adhoc but I can see why they exist considering the ecosystem which "just ended up that way".
Fast-Nop2702823dIt's also a history of bloating up both the toolchains and the end product with ever more stupid shit. We're now at the point where 500 bytes of text "need" 3MB over the wire and drain the batteries of mobile devices.
On the upside, 90% of that shit is superfluous anyway. It's only there because retarded frontend shitheads behaved like toddlers in a candy store.
Making lean and fast products increasingly gives you an edge because users just bounce off of slow websites. Therefore, the bloat costs real money.
Microsoft has made the next step of this in "Blazor." Full steam ahead on web assembly, applications running on top of mono.wasm, then loading an aspnet application on top of it. All so a bunch of children don't have to learn anything new.
It's like someone woke up one day and thought, "you know what'd be cool? Making my users download a 3mb runtime before they even glance at my application."