Login
You're viewing the functional.cafe public feed.
  • Oct 7, 2026, 8:15 PM

    Many years ago I used to work on a Cobol-based application that ran over an 80x25 green screen terminal. People running 30 or 40 users on a 486 PC running SCO Unix hooked up to a multi-port serial card.

    We'd never have tolerated the amount of waiting between actions or screens that is now considered absolutely normal on web-based cloud-hosted applications.

    Weird how things change.

    💬 6🔄 76⭐ 23

Replies

  • 💬 1🔄 0⭐ 0
  • Oct 8, 2026, 1:06 AM

    @ben That's pretty quick.

    Yesterday I was using a web-based search and I thought it was broken because I applied a filter and it happened too fast for me to notice. 😄

    💬 0🔄 0⭐ 0
  • Colin WSeedoubleya@mastodon.nz
    Oct 8, 2026, 1:13 AM

    @thomasbeagle you remind me of my reluctant involvement in a recent migration from ugly green screen ERP system to mumble something Microsoft. I’m not sure how the company survived the productivity loss. The project nearly killed me and of course those that pushed through the decision on product choice long gone and only the chaos remains.

    💬 0🔄 1⭐ 8
  • 💬 0🔄 1⭐ 8
  • 💬 0🔄 0⭐ 0
  • Emelia/Emibecomethewaifu@tech.lgbt
    Oct 8, 2026, 1:56 AM

    @thomasbeagle Speaking as someone that occasionally still interacts with one such green-screen application occasionally, and its lightning-fast responses, it's genuinely disturbing how nobody seems to give even the slightest shit about response-time optimization in "modern" apps these days...

    (Hell, that lack of care has even infected transit cards... Y'know, the thing that kinda needs to be fast to avoid the gate lines becoming a tangled mass of humans? The older ones here can be tapped in about 200-400ms, usually fast enough to hit it at walking pace without slowing down. The new ones? Take upwards of an entire second to even acknowledge the card. And that's one of the less bad complete UX failures in the system...)

    💬 2🔄 4⭐ 0
  • Stuck_HereStuck_Here@c.im
    Oct 9, 2026, 1:39 AM

    @becomethewaifu @thomasbeagle

    In the 90s and early 00s I'd read articles on the industry where they were doing all they could to speed up boot times, web page loads, and all the rest.

    Now I visit a webpage and 8 to 12 seconds will unfold with elements on the screen buffering while security protocols are checked, computing power from my CPU is accessed, roustabouts take an early lunch lounging all over the memory chips, deranged chimps crank furiously to speed up my cooling fan, and men in trench coats take a peak into my hard drive.

    💬 0🔄 2⭐ 11
  • Oct 10, 2026, 9:17 AM

    @Stuck_Here @becomethewaifu @thomasbeagle

    I remember a study by Google where they found the bounce rate significantly increased if a page took over something like 200 ms to load. People were worried about adding TLS adding a couple of extra network round trips to the network would get into this window.

    Now, a load of popular sites load more slowly than their equivalents did back when I used a 26.4 Kb/s MODEM (fastest speed it would normally connect at the very end of a rural phone line).

    💬 0🔄 0⭐ 0
  • Oct 9, 2026, 12:37 PM

    @becomethewaifu

    There are too many layers of abstraction and almost nobody has any understanding of the hardware or operating system basics so they can't optimise stuff effectively.

    @thomasbeagle

    💬 0🔄 0⭐ 0
  • Oct 10, 2026, 9:33 AM

    @zl2tod @becomethewaifu @thomasbeagle

    I don’t like to blame abstraction because good abstractions are crucial to building performant systems. No one can have in-depth knowledge of how to optimise every layer in the stack.

    The problem is that many of the abstraction layers are built either for a set of requirements that no longer exist or with no reference to the needs of the layers above.

    To take a trivial example:

    OpenStep (1994, later rebranded as Cocoa by Apple) has an incredibly rich view class for editing text. It gives you a zero-effort way of providing a plain or rich-text editing functionality but also gives you hooks to plug into any aspect of the layout pipeline. You can precisely control kerning, define the shapes that text will wrap into, replace the hyphenation algorithm with one of your own, and so on. It integrates with the native scroll view, so it’s easy to render large amounts of editable text that exceed the size of the screen. 90% of uses just pick the default. 99% are handled by just setting attributes on ranges in the text that users provide. The remaining 1% use the fine-grained control. This means that basically every native Mac app gets to reuse the same code. It spent a couple of decades getting optimisations and rich text editing is smooth and consistent across all Mac apps that don’t use Electron.

    Now contrast this with web apps. The web provides a native plain text editing box that gives almost no control over the contents. It provides a rendering tree for things in the DOM that you can control. But if you want to create an editing view for rich text (especially if you want it to have custom semantics), you don’t have a good common abstraction. So everyone implements their own, using bits of JavaScript that go and produce terrifyingly layered things in the DOM. And this is much slower than a native rich text view on macOS.

    💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 1
  • Oct 9, 2026, 3:39 AM

    @EA4GMZ @thomasbeagle yes, because everyone knew old computers were slow, so the latency had to be short to give the illusion of speed

    now we know computers are fast, and nobody cares about latency any more.

    progress, right? 🤦‍♀️

    (obligatory disclaimer: this post might not be historically accurate)

    💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Oct 10, 2026, 9:37 AM

    @EA4GMZ @thomasbeagle

    The round trip time from me to the nearest Azure datacenter is around 10ms. This is fast enough that I can run a game on an Xbox that is running there and stream back the result. Every button press or other controller interaction goes via Bluetooth to a local machine, is encrypted, sent TLS encrypted to the datacentre, decrypted, processed on the target Xbox, then a frame is rendered, compressed (as video, with unidirectional interframe compression), encrypted, sent out over the network, decrypted at my end, sent over HDMI, and displayed. And this happens with low enough latency that I don’t notice that the game is not local.

    The new computers are not the problem.

    💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 4
  • 💬 0🔄 0⭐ 3
  • Oct 8, 2026, 10:28 PM

    @thomasbeagle And at least you can look at the description of the image in alt="ABCXYZ" while you're waiting for it to load to see if it's worth waiting or just go on reading the rest of the page.

    💬 0🔄 0⭐ 2
  • 💬 0🔄 0⭐ 0
  • Oct 9, 2026, 1:34 PM

    @thomasbeagle I remember our sys admin refusing to install that memory intensive screen editor everyone loved because we had that many on a PDP-11 running Unix. Oh vi not emacs. Yes I remember those days too.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 1⭐ 0