I’m curious how software can be created and evolve over time. I’m afraid that at some point, we’ll realize there are issues with the software we’re using that can only be remedied by massive changes or a complete rewrite.

Are there any instances of this happening? Where something is designed with a flaw that doesn’t get realized until much later, necessitating scrapping the whole thing and starting from scratch?

  • gnuhaut@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    7 months ago

    GUI toolkits like Qt and Gtk. I can’t tell you how to do it better, but something is definitely wrong with the standard class hierarchy framework model these things adhere to. Someday someone will figure out a better way to write GUIs (or maybe that already exists and I’m unaware) and that new approach will take over eventually, and all the GUI toolkits will have to be scrapped or rewritten completely.

      • Joe Breuer@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        7 months ago

        Which - in my considered opinion - makes them so much worse.

        Is it because writing native UI on all current systems I’m aware of is still worse than in the times of NeXTStep with Interface Builder, Objective C, and their class libraries?

        And/or is it because it allows (perceived) lower-cost “web developers” to be tasked with “native” client UI?

          • Joe Breuer@lemmy.ml
            link
            fedilink
            arrow-up
            1
            ·
            20 days ago

            Aware, yes. Interested, no - closed source philosophy, and the way Apple implements it specifically, turn me off hard.