• 1 Post
  • 599 Comments
Joined 1 year ago
cake
Cake day: August 17th, 2023

help-circle






  • Well if it were closed source, it would be harder to repackage proprietary apps because you would not know how the snap “root filesystem” translates to $DISTRO root filesystem.

    Only if all the other tools (like Snapcraft) were also made closed-source and obfuscated, but that’s besides the point. What if, for example, Snaps start costing money, and you can’t legally turn them into Flatpaks and distribute them? What if the only legal way to get some software for Linux will be the official Snap repository? This approach will make for a far worse user experience than simply using the already working, already open-source and non-enshittifiable alternative.

    Because some apps are only packaged as snaps so if you want them to be accessible to users, you have to install snapd. Flatpak can still be the default which on non-Canonical distros already is. Which why I don’t even worry about snap becoming the standard.

    And by promoting Snap to the same status as Flatpaks on other distributions, you’re opening the gates for enshittification and a worse user experience tomorrow. Again, why support it as an equal option if we all know the price?






  • When I wrote that I was imagining something more significant like a code refactor,

    Again, a code refactor is not a change in public API and thus does not constitute a semver major bump.

    I’d like to have written a more constructive reply, but with most of your comment consisting of explanations with arguments couched in I’m not interested enough to parse out what is what, sorry. Don’t know why you explain UserChrome.css to me.



  • I think you have a misconception about what Semver is. No, changing private interfaces does NOT increase major version - why do you think that Semver specifies that you must declare a public API? This would also mean any bugfixes would result in major bumps, but they don’t, because not every interface change is treated equally.

    You also skipped the actual question. What are all of Firefoxes interfaces? Is user flow itself an interface?


  • FooBarrington@lemmy.worldtoFirefox@lemmy.mlFirefox 132.0.1 Release Notes
    link
    fedilink
    arrow-up
    1
    arrow-down
    2
    ·
    edit-2
    9 days ago

    That works for libraries, but applications? What is the interface you’re looking at for backwards compatibility? Towards websites, towards workflows, towards CLI arguments, towards ABI, or something else?

    There’s also the disadvantage of being perceived as moving slower than the competition. If Chrome is at v162 and you’re at v3, people perceive the version numbers to reflect the quality and development. Shouldn’t be the case, but it is.