Beyond enshittification, why does tech oftentimes suck? - eviltoast

Sometimes I’ll run into a baffling issue with a tech product — be it headphones, Google apps like maps or its search features, Apple products, Spotify, other apps, and so on — and when I look for solutions online I sometimes discover this has been an issue for years. Sometimes for many many years.

These tech companies are sometimes ENORMOUS. How is it that these issues persist? Why do some things end up being so inefficient, unintuitive, or clunky? Why do I catch myself saying “oh my dear fucking lord” under my breath so often when I use tech?

Are there no employees who check forums? Does the architecture become so huge and messy that something seemingly simple is actually super hard to fix? Do these companies not have teams that test this stuff?

Why is it so pervasive? And why does some of it seem to be ignored for literal years? Sometimes even a decade!

Is it all due to enshittification? Do they trap us in as users and then stop giving a shit? Or is there more to it than that?

  • mycodesucks@lemmy.world
    link
    fedilink
    arrow-up
    13
    ·
    2 months ago

    It doesn’t help that every new generation adds a new blackbox abstraction layer with little to no end-user benefit, the possibility of duplicated functionality and poor implementation, security concerns, poor support, and requiring a flashy new CPU with system crashing speed tricks to maintain a responsive environment through 12 levels of interpreters.

      • mycodesucks@lemmy.world
        link
        fedilink
        arrow-up
        7
        ·
        edit-2
        2 months ago

        No, the OSI model is fine.

        I’m talking more about sandboxing an interpreted app that runs a container that runs another sandboxed interpreted app, both running their own instances of their interpreter with their own dependencies and accessible through a web interface that is accessible through yet another container running a web server that is running in Python with a virtual environment despite being the only Python app on the container, which is then connected to from another sandboxed tab on a sandboxed browser on your machine.

        But hey, at least it isn’t, god forbid, a MONOLITH. That would require someone to take the time to understand how the application works.

        • AdNecrias@lemmy.pt
          link
          fedilink
          arrow-up
          2
          arrow-down
          1
          ·
          2 months ago

          Ah, yeah I get that. Java interpreter so you can virtual machine your way into having someone else making sure the thing works with all hardware it can live in.

          Blind scalability and flexibility are neat tho, gives access to a lot less knowledgeable people to do stuff and theoretically frees up those who know for more complicated tasks.

          • msage@programming.dev
            link
            fedilink
            arrow-up
            2
            ·
            2 months ago

            It almost never works like that.

            People who don’t understand computers will work against it in almost every case.