FWIW I have experienced a little jank with Parcel when I tried it a couple years ago but I have never experienced jank with Vite in the few medium-size projects I've used it in
@DLosc In Maharashtra, or at least in Mumbai+Pune, it's pretty standard for a kid to be given their father's first name as their middle name, and woman are supposed to change their middle name to their husband's first name when they marry
I know my grandma had to change her first name to one chosen by her in-laws too, but thankfully that's not done anymore
Well the only other idea I can find at this time is this:
> To improve the build time when using ts-loader, use the transpileOnly loader option. On its own, this option turns off type checking. To gain type checking again, use the ForkTsCheckerWebpackPlugin. This speeds up TypeScript type checking and ESLint linting by moving each to a separate process.
Other than that, I guess webpack really might be that slow
for anything other than systems/embedded programming i would prefer a GC'd language unless the GC provably causes undesirable lag
(yeah i know the discord example, that was justified, but only because they did empirical measurements to justify their example and not because "rust is gud")
Yes, porting an algorithm from one language to another won't increase speed much (unless you're one of the few hundred people on the planet who understands how to optimise L1 cache lookups). But when people rewrite something completely with plans to redesign the majority of the project for performance, they generally use a more performant language because they can.
