Also, I would enforce every online shop, transport company, hotels… All of these functioning under a federated market, sort of like the fediverse. Impossible to corrupt. Impossible to monopolize. True choice.
What’s with Git? Sure, it is used by a lot of people, but it has some of it’s own shortcomings as a snapshot-based version control. VCS like Pijul has it’s own advantages, something to do with the patch theory of differences (disclaimer: I’m not an expert in this).
I am also kinda opposed to enforcing XDG, because of how unstandardized it is. Like for example, to set a terminal, GNOME Shell had to hardwired a piece of code to their internals, checking to see if a particular environment variable exists, , or else use gnome-terminal, which is just bad practise.
Most of the time. I use calendar versioning (calver) for my internal application releases because I work in IT. When the release happens is more consequential than breaking changes. And because it’s IT, changes that break something somewhere are incredibly frequent, so we would constantly be releasing “major” versions that aren’t really major versions at all.
OpenDocument.
Agreed compared to .doc and .docx. And if you’re going to version control it, markdown instead of a binary blob.
For academic documents in STEM fields, I’d love to see a transition from LaTeX to Typst. Much cleaner, better error handling, and it has a web UI if people don’t want to install a massive runtime on their own computer.
Yeah, Typist is great and has potential for much more still! The big issue is something like the network effect, LaTeX has everything you could possibly want, pretty much, and people will continue to primarily support it because it’s the biggest tool. It will be hard to break that cycle, but in the long run it may be possible.
Also, I would enforce every online shop, transport company, hotels… All of these functioning under a federated market, sort of like the fediverse. Impossible to corrupt. Impossible to monopolize. True choice.
You would be surprised.
Hold my briefcase
What’s with Git? Sure, it is used by a lot of people, but it has some of it’s own shortcomings as a snapshot-based version control. VCS like Pijul has it’s own advantages, something to do with the patch theory of differences (disclaimer: I’m not an expert in this).
I am also kinda opposed to enforcing XDG, because of how unstandardized it is. Like for example, to set a terminal, GNOME Shell had to hardwired a piece of code to their internals, checking to see if a particular environment variable exists, , or else use gnome-terminal, which is just bad practise.
Most of the time. I use calendar versioning (calver) for my internal application releases because I work in IT. When the release happens is more consequential than breaking changes. And because it’s IT, changes that break something somewhere are incredibly frequent, so we would constantly be releasing “major” versions that aren’t really major versions at all.
Agreed compared to .doc and .docx. And if you’re going to version control it, markdown instead of a binary blob.
For academic documents in STEM fields, I’d love to see a transition from LaTeX to Typst. Much cleaner, better error handling, and it has a web UI if people don’t want to install a massive runtime on their own computer.
Yeah, Typist is great and has potential for much more still! The big issue is something like the network effect, LaTeX has everything you could possibly want, pretty much, and people will continue to primarily support it because it’s the biggest tool. It will be hard to break that cycle, but in the long run it may be possible.
I understand the de facto standard situation, but I’d rather have Fossil as default as long as it’s suitable.
Defined by an env variable? How asinine!