News for hackers. Stuff that matters.
Re:Breaking up with JavaScript front ends by afavour on Saturday December 10, 2022 @10:51PM (#33939876)
> This kinda crap is why the gmail tab uses a GB of memory.

It isn’t. Ironically things like memory leaks are why pages use a ton of memory and in my experience everyone coding from scratch results in more of them, not less.

Re:Breaking up with JavaScript front ends by t8sr on Sunday December 11, 2022 @01:34AM (#33940690)
I really don’t agree. When I worked at Google, I filed a couple of bugs for memory leaks in the new gmail, and to my knowledge they still haven’t been addressed two years later, because there are a million dependencies and the thing is so complex no one can debug it, or even come up with a reliable repro.
Re:Breaking up with JavaScript front ends by sph on Sunday December 11, 2022 @02:10AM (#33940910)
Memory leaks, like bugs, tend to scale linearly with code size. You better believe your 100k line framework has more leaks than my 1000 line script.
Re:Breaking up with JavaScript front ends by afavour on Sunday December 11, 2022 @09:15AM (#33943364)
Strong disagree. Frameworks are almost always going to be better profiled, better tested and have more eyes than any home crafted code. The number of lines isn’t really that relevant.