I’m not sure that it can be clearly delineated as a time loop or a causality loop, it’s honestly a mix of both - though you’d probably call it a causality loop, as each “instance of a person” only experiences the loop once.
What about stories about time travel that ultimately form a closed loop? There’s one that has people moving forwards and backwards through time, yet forms a closed loop at the end: >!Dark!<
Man, your dad must have had you early, two children before 9…
Imagine you can set a theme of your choice like “Star Trek technobabble” for little explanations for the delay.
“Delay due to chirality recalibration of phase discriminating amplifier for positronic brain…”
Might literally be one of the best use cases I’ve seen so far!
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?
I’m aware, it was mostly a joke about these “features” making Notepad worse. Nevertheless, thank you :)
More like Notepad–, amirite
Who the fuck wants Carmilla of Styria to win. She’ll never be satisfied, always clawing for more. There is no winning with her, only not having lost so far.
Let’s go with the Cambridge definition:
a perfect society in which people work well with each other and are happy
The Oxford Languages definition is incomplete enough to not be a valid counter argument - “perfect” doesn’t mean everyone 100% gets what they want. The only sensible interpretation is “perfect” from a societal perspective.
But if yes, then as long as current conditions meet anyone’s definition of utopia, then we’re all living in one.
No, Utopia has a defined set of meanings. If current conditions meet someone’s definition of Utopia, but doesn’t meet the defined set of meanings, it doesn’t mean current conditions are Utopia.
“Utopia” doesn’t mean everyone gets what they want. People can want things to be worse while still living in a Utopia.
Okay, and how does snapd being open source help with that? It literally has no effect on it.
And when your best argument is “if it gets enshittified you can switch off of it”, why help it get popular in the first place?
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.
All the feedback and attempts at studies I’ve seen point in the opposite direction, don’t know what to tell you.
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?
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.
Ooooh boy, that’s a nice one, almost got me!