FOSS projects arbitrarily breaking their own backwards compatibility, a mini-story
Me: *watching a video about five Linux terminal emulators the channel host likes*
Me: *sees a terminal emulator I might like, goes to check if it has the config options I want*
Said terminal emulator: We've already changed how our app stores its config! It's not YAML anymore! It's TOML! 🥰
Me: WTF is TOML??? *looks it up* ....... what the fuck this is literally just Windows INI file format. 😒
re: FOSS projects arbitrarily breaking their own backwards compatibility, a mini-story
@dragonarchitect Oh jeez which term is it? I'd prefer to avoid that.
re: FOSS projects arbitrarily breaking their own backwards compatibility, a mini-story
Sounds like they're leaning into the "we're not 1.0/stable yet" versioning thing which is common enough and semantic versioning community standards vary. But it's a great sign that they're for people who like their computers changing on them after updates vs continuing to do what they want, which I'm not sure was ever me.
re: FOSS projects arbitrarily breaking their own backwards compatibility, a mini-story
@gravepapaya I legit don't have the spoons to deal with sudden major changes to a thing that don't have a damn good and logically defensible reason behind it.
Especially if the thing has worked Perfectly Fine until the sudden change, because that just completely evaporates my working knowledge and memory of the thing and forces me back to square one again.
If it's something integral to my workflow, that SUCKS
re: FOSS projects arbitrarily breaking their own backwards compatibility, a mini-story
@dragonarchitect
Yep. And for me it doesn't even matter if they have great reasons for the change (barring security being totally screwed without it), I now like nice 10 year support lifecycles where things won't change.
At work it was maddening when infrastructure would change underneath me forcing me to set up portions of my workstation again vs doing work.
re: FOSS projects arbitrarily breaking their own backwards compatibility, a mini-story
@renbymon Alacritty, apparently. They switched from YAML to TOML for their config files as of 0.13.0
You would think that something like this would qualify as an API break and force a bump in the major release number, because it forces/requires a complete port of config files to the new format!! But nooooooooo