• marmulak@lemmy.ml
    link
    fedilink
    arrow-up
    6
    ·
    3 years ago

    I find those points of theirs to be pretty weak.

    1. With Flatpak most of the runtime stuff is packaged separately, so on Flathub for example you have most of the applications using common runtime components. Sometimes you need multiple versions of one of them, but the same goes for a lot of Microsoft’s stuff.
    2. I don’t find Windows to be any more backwards compatible than Linux is. On Linux you get the advantage of having access to the source more often, so source is going to be compatible for longer than binaries will. Source can be updated for compatibility too, giving it infinite life. (Of course, binaries could have infinite life if you take into account all the compatibility methods like virtualization.)
    3. Yeah I’m sure business just love using ancient proprietary software and not being able to upgrade their systems. Oh wait, I thought compatibility was strong on Windows. (Not that all such software runs on Windows, but of course a major chunk of it does.) Businesses will eventually have to replace that old stuff, whether it’s sooner or later. It would have been better if they had the source code in the first place and could use that to help them upgrade or replace it.
    • pinknoise@lemmy.ml
      link
      fedilink
      arrow-up
      5
      ·
      3 years ago

      With Flatpak most of the runtime stuff is packaged separately

      They mentioned that not all flatpaks use the same separate runtime. Ideally they could just use the one my distro packages.

      I don’t find Windows to be any more backwards compatible than Linux is. On Linux you get the advantage of having access to the source

      You can run (a lot of) really old (late 90s) windows binaries with the modern libraries. You can also probably run really old linux binaries, but only if they use syscalls directly, not if they are (dynamically) linked against e.g. libc or x-stuff. Of course if the source is open, you can make it work.