"Windows 95 was 30 MB" is such an ignorant, obnoxious, trite take. a triple buffered framebuffer (which you want for smooth scrolling) for my 4K display is 70 MB in *pixels alone*. Obviously a complete webpage with precomposed textures would take more.https://twitter.com/julienPauli/status/1042113172143067138 …
-
Show this thread
-
Replying to @whitequark
"Precomposed textures" doesn't sound very reasonable for a webpage. I can't think of any good reason for a webpage whose purpose isn't delivering high-res media to be more than a few hundred kB.
1 reply 0 retweets 12 likes -
Replying to @RichFelker
The current generation of browsers is optimizing for input latency at cost of memory consumption, which is a tradeoff that isn't right for everyone (probably not for you!) but is a decision that should be acknowledged as valid
2 replies 1 retweet 27 likes -
Replying to @whitequark @RichFelker
The same tech nostalgia people are often using low input latency of 40-year-old emacs (or whatever) as an example of how that tech is good, and I agree! Low input latency is important. Moderate RAM use is how we do this for webpages, and that is not inherently wrong.
2 replies 1 retweet 22 likes -
Replying to @whitequark @RichFelker
They clearly don't use emacs on a day to day basis. I love it but make a line longer than 250 chars and that gap buffer implementation slows it to a crawl
1 reply 0 retweets 9 likes -
Replying to @SerialDev @whitequark
Gap buffer is a bad design, but there's no excuse for long lines.
2 replies 0 retweets 1 like
And FYI I do use emacs on a daily basis. This is nothing like nonsensical comparisons with Win95 which is unusable. Emacs is a maintained piece of software with ongoing nice developments.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.