diff --git a/content/posts/first-pcb.md b/content/posts/first-pcb.md index d3358cc..9695136 100644 --- a/content/posts/first-pcb.md +++ b/content/posts/first-pcb.md @@ -1,5 +1,6 @@ +++ title = "My first PCB" +draft = true date = 2026-03-25 updated = 2026-03-25 diff --git a/content/posts/why-versioning-is-important.md b/content/posts/why-versioning-is-important.md index 61b574a..933d89f 100644 --- a/content/posts/why-versioning-is-important.md +++ b/content/posts/why-versioning-is-important.md @@ -15,15 +15,15 @@ Their current system is as follows: Every minor version is where Mojang implemen ## What's wrong -So, Minecraft doesn't really follow Semver, who cares? My first mod, [Simple armor hud](https://github.com/legoraft/simple-armor-hud/releases), also didn't follow it very well, and to be honest, it doesn't matter a lot. The problem has started with the new changes. The issues begin with the fact that the Semver major version never changes, which removes a lot of flexibility for versioning. This is why the last number is now reserved for feature drops _and_ bug-fixes. If Mojang would truly follow Semver, they wouldn't remove backwards compatibility when they update the minor version (which is their major version). +So, Minecraft doesn't really follow Semver, who cares? My first mod, [Simple armor hud](https://github.com/legoraft/simple-armor-hud/releases), also doesn't follow it very well, and to be honest, it doesn't matter a lot. The problem has started with the new changes. The issues begin with the fact that the Semver major version never changes, which removes a lot of flexibility for versioning. This is why the last number is now reserved for feature drops _and_ bugfixes. If Mojang would truly follow Semver, they wouldn't remove backwards compatibility when they update the minor version (which is their major version). -The most recent change in the update cycle of Minecraft causes the bug-fix version to be completely neglected. They want to drop new (incompatible) updates on every minor version bump, while also still pushing bug-fixes to this version. This means that `1.21.2` can be the version in which the bundles are added ([24w39a](https://www.minecraft.net/en-us/article/minecraft-snapshot-24w39a)), or be a simple bug fix version that's backwards compatible. This removes a lot of the information you can get from a Semver spec version. Even though it's annoying, this isn't a big problem. +The most recent change in the update cycle of Minecraft causes the bugfix version to be completely neglected. They want to drop new (incompatible) updates on every minor version bump, while also still pushing bugfixes to this version. This means that `1.21.2` can be the version in which the bundles are added ([24w39a](https://www.minecraft.net/en-us/article/minecraft-snapshot-24w39a)), or be a simple bugfix version that's backwards compatible. This removes a lot of the information you can get from a Semver spec version. Even though it's annoying, this isn't a big problem. ## The problem -The versioning won't hurt a lot of people. If you want to play Minecraft, open the most recent version and play it. Some people, like me, will be a bit annoyed by the fact that you can't get a lot of information from the Semver version. The biggest issue affects developers. +The versioning won't hurt a lot of people. If you want to play Minecraft, open the most recent version and play it. Some people, like me, will be a bit annoyed by the fact that you can't get a lot of information from the Semver version. The biggest issues are for developers. -Before this change, if you built a mod for `1.21`, you could (mostly) count on it working for every bug-fix version after that. This is often called `1.21.x` support. After this change, mod developers will need to rewrite their mod a lot on every minor version. This means that mods probably won't support every minor version from now on. This can cause developers to drop out or players to get annoyed because mod development just isn't that fast. +Before this change, if you built a mod for `1.21`, you could (mostly) count on it working for every bugfix version after that. This is often called `1.21.x` support. After this change, mod developers will need to rewrite their mod a lot on every minor version. This means that mods probably won't support every minor version from now on. This can cause developers to drop out or players to get annoyed because mod development just isn't that fast. The biggest example of this is masa, he's the brain behind mods like litematica, minihud and tweakeroo. After this change by Mojang in versioning became apparent, he [announced](https://www.reddit.com/r/litematica/comments/1di4o3h/announcement_about_litematicas_future_and_updates/) that he'll stop developing his mods for newer versions. Mojang also has been a lot more radical with code changes, meaning that a rewrite sometimes isn't just adjusting a few variables, but needing to understand a whole new system. @@ -31,7 +31,7 @@ Mod development is slowing down for people who do this in their free time. I've ## Solutions -To be fair, I don't think that Mojang will change Minecrafts versioning system. The subset of people who have problems with their new feature drops is way too small to care about. Besides, Mojang has been giving the Minecraft updates names for quite some time. This means that the usual “I play Minecraft `1.21`.” can be replaced by “I play the **Tricky Trials** update.” I just happen to like the version names. I do want to propose a versioning solution though. +To be fair, I don't think that Mojang will change Minecrafts versioning system. The subset of people who have problems with their new feature drops is way too small to care about. Besides, Mojang has been giving its updates names for quite some time. This means that the usual “I play Minecraft `1.21`.” can be replaced by “I play the Tricky Trials update.” I just happen to like the version names. I do want to propose a versioning solution though. The simplest solution to bring back real bug fix versions would be to start using the major release number, so `1.21.1` turns into `21.0.1` if it was a bug fix version, and `21.1.0` if it was an extra feature drop. Mojang can also add tags to their version names, like `1.21.1-bug0` or something like that. These solutions are just quick fixes, and as I've said before, I don't think Mojang will change this.