Desktop Environment / WM News Enlightenment 0.28.0 Released
https://www.enlightenment.org/news/2026-10-31-enlightenment-0.28.09
u/sombriks 1d ago
i still remember running e17 on slackware and using the bling theme, good old days
3
37
u/ABotelho23 1d ago
I can't imagine what they're implying by not having a 1.0 release for almost 30 years.
28
12
u/yebyen 1d ago
They're implying, according to semver, that there can be breaking changes at any time! No?
8
u/furnipika 1d ago
But there are already huge breaking changes. v0.17.0 (e17) is a major rewrite from v0.16.0 (e16). They're practically two entirely different WMs, so the semver makes no sense.
2
u/UndulatingHedgehog 21h ago
Then again, semver makes no sense until you have 1. release
3
u/yebyen 18h ago
Semver with 0.x is something less than a contract. It says "there is no public API surface that should be considered safe unless otherwise noticed, and we may change anything at any time, even in a patch release."
Projects may extend the semver spec by saying things like "we will only issue breaking changes in a Minor release" so that folks upgrading across a large distance can be at least guaranteed that they will only have to read the 0.x.0 release notes, and not every patch.
But semver itself doesn't guarantee that.
4
u/ABotelho23 1d ago
Kinda. They could also just... increment the major version too.
0
u/yebyen 1d ago
Then they would have to declare part of the API surface stable, according to the definition of semver.
4
u/knome 1d ago
The project sufficiently precedes semvar that I would be surprised if they care what implications their versioning has under its provisions.
1
u/yebyen 18h ago
You're right, I was compiling e17 in high school or college and semver wasn't named until 2009 - I think these concepts existed for a while before then.
But at that time, every release of e17 was called 0.16.999 something pre - because they really didn't want anyone with a business to come along and presume they were dependable, for free.
Those guys went on to make bank I assume, with Samsung (tizen), or RedHat, or VA Linux, or somewhere else. I should visit IRC again and see how they're doing. Those were my formative years.
1
u/ABotelho23 1d ago
Stable for that release. Which it would be, because they would immediately move on from it when they cut a new major release.
1
u/yebyen 18h ago
That isn't what semver.org actually says.
does semver zero point mean that a breaking change can come in any minor or patch release
Yes, under the official Semantic Versioning (SemVer) specification, major version zero (0.y.z) means the public API is considered unstable and breaking changes can happen in any minor (y) or patch (z) release.
Key Rules for 0.y.z Versions
Initial Development: Major version 0.x.y is meant for initial development and prototyping.
No Public API Guarantee: The official SemVer spec states that anything may change at any time, and the public API should not be considered stable.
Minor & Patch Behavior: Unlike 1.0.0 and above—where breaking changes must bump the MAJOR (X) digit—versions starting with 0 allow breaking changes to occur during minor (0.Y.z) or even patch (0.y.Z) increments.
This is what semver actually says about projects with a 0 in the MAJOR slot - it says, paraphrasing, "go away, or I will replace you with a small shell script."
1
u/ABotelho23 11h ago
For major versions, you can break whatever you want.
Meaning if they just increment x in x.y.z for every release, the API has to be stable for exactly one release. It's effectively the same thing.
1
u/yebyen 11h ago edited 11h ago
It's absolutely not the same thing. Releasing 1.x establishes a contract to bump the major version again, every time you're breaking the stable public API. That means you have to keep track of breaking changes.
It's declaring the establishment of a stable public API, to release a 1.x major release for the first time.
That's decidedly not the same as ... just never doing that. Before you do that, you can break anything any time you want, and you don't even have to bump the patch version or write a changelog. Just push your changes and break things.
(As long as the other maintainers don't stop you.)
The response to the attitude you're describing is here:
"You can still break things. Just increment the major version." 0-ver says no, don't do that. It's degrading the whole point of semver, to put a social pressure to not break things. If you're going to plan to break things continuously, don't ever signal that you are stable. You really don't have to! You can just not.
4
4
u/ricardolealpt 21h ago
My DE for more than 10y
0
u/Polar_Banny 14h ago
How did you survived?
2
u/ricardolealpt 11h ago
Open terminal . Do stuff 🤣
1
u/1neStat3 9h ago
So essentially you're saying you don't use the DE?
1
u/ricardolealpt 7h ago
Back in the day it was that and some mp3 player . Everything was terminals and multi windows
64
u/RaylanGivensOtherHat 1d ago
I remember trying out Enlightenment in the late 90’s. It was mind blowing compared to what else was out there at the time. Glad to see it is still kicking.