• _stranger_@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    4
    ·
    2 months ago

    I don’t think y’all understand. Software is never done, it just becomes abandoned. You have been a “tester” for every piece of software you’ve ever used. And that’s a good thing, because the alternative is you get stuck with whatever the first version is. No one wants dead software.

    • Sentau@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 months ago

      There is a difference between software getting updated and software getting fixed though. We want the first scenario not the second one

      • _stranger_@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        2 months ago

        Not a lot of options there. You either go with an old pre-computer car or get an open source car (which isn’t really an option).

        I’m not talking about the infotainment system, just to be clear. I’m talking about the software that controls the functions of the drive and safety systems. If you want an infotainment system that you have complete control over, I’d suggest putting an open source tablet on your dash

        https://itsfoss.com/linux-tablets/

        Sadly, it looks like most of the FOSS car infotainment projects died a few years ago.

          • _stranger_@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            2 months ago

            Nope. If you want control over what’s getting done to your software, you’ve got to take ownership of it, or you might get changes in your fixes you’re not happy with.

            • Sentau@discuss.tchncs.de
              link
              fedilink
              English
              arrow-up
              1
              ·
              2 months ago

              Well my comment was not about having control over the software/firmware though that will be cool.

              My logic is that well tested, polished software/firmware have very few bugs and hence most of the updates they get are feature additions or improvements to current functionality (examples in an EV could be updates making the BMS more robust, tweaking the regen modes according to feedback from the users, etc). Poorly tested, half baked software/firmware will be full of bugs and broken functionality and will lead to ‘updates’ where all the changes are correcting broken functionality and serious bugs. This will be an unpleasant experience for the user and we should hold companies accountable when they do shit like this