floathub 23 minutes ago Emacs text interface, Emacs GUI interface, and ... sorry what's the third one? :-) iron-s 18 minutes ago ghostty running ssh w/ emacsclient connected to emacs daemon running ghostel
GianFabien 34 minutes ago Early Reuters and Bloomberg terminals had a text-centric aesthetic.AFAIK on a PC, when booted into text-only mode, you are still using a bit-mapped framebuffer. From my experiments you can mix graphics and text.
hypfer 21 minutes ago Ah yes, website talks about "the bloat of x11 and Wayland", and doesn't even scroll correctly on Firefox mobile likely due to some JavaScript fuckery.Practice what you preach. And practice first. dormo 18 minutes ago Scrolling is pretty bad on Firefox desktop as well. So bad that I didn't want to finish the article.Why do people do this? orangea 5 minutes ago I don't see any suspicious JS on the page, so I suspect it's a styling issue triggering some inefficiency in Firefox. There are animations and text-shadows.
dormo 18 minutes ago Scrolling is pretty bad on Firefox desktop as well. So bad that I didn't want to finish the article.Why do people do this?
orangea 5 minutes ago I don't see any suspicious JS on the page, so I suspect it's a styling issue triggering some inefficiency in Firefox. There are animations and text-shadows.
Isn’t that what resolution aware ttys and screen accomplish?
Emacs text interface, Emacs GUI interface, and ... sorry what's the third one? :-)
ghostty running ssh w/ emacsclient connected to emacs daemon running ghostel
Early Reuters and Bloomberg terminals had a text-centric aesthetic.
AFAIK on a PC, when booted into text-only mode, you are still using a bit-mapped framebuffer. From my experiments you can mix graphics and text.
Well, if we count claude as tui.
Like the days of Norton Commander
Ah yes, website talks about "the bloat of x11 and Wayland", and doesn't even scroll correctly on Firefox mobile likely due to some JavaScript fuckery.
Practice what you preach. And practice first.
Scrolling is pretty bad on Firefox desktop as well. So bad that I didn't want to finish the article.
Why do people do this?
I don't see any suspicious JS on the page, so I suspect it's a styling issue triggering some inefficiency in Firefox. There are animations and text-shadows.