Dumbest thing in software imo, is when I see software that is obviously worthy of being out of v0 (beta, alpha, etc), stay in v0.
Though since it still is v0, I guess we can’t expect much.
Not sure why it is, maybe there is a good reason, but the software functions well enough for a stable release, though at the same time, this is a very small scale operation with great ambitions and a big userbase. If you api needs to be updated, it’s obviously much easier to just push a breaking change than to maintain a migration period.
There’s a lot of nuance, but I’d like more software to just enter v1 when it works as intended and then breaking changes can increment the major version rather than staying in v0 which is harder to tell when a breaking change happens.
p.s. so far config changes in hyprland have only been a 5 min fix so i haven’t experienced this fuss yet, maybe soon!
Dumbest thing in software imo, is when I see software that is obviously worthy of being out of v0 (beta, alpha, etc), stay in v0.
Though since it still is v0, I guess we can’t expect much.
Not sure why it is, maybe there is a good reason, but the software functions well enough for a stable release, though at the same time, this is a very small scale operation with great ambitions and a big userbase. If you api needs to be updated, it’s obviously much easier to just push a breaking change than to maintain a migration period.
There’s a lot of nuance, but I’d like more software to just enter v1 when it works as intended and then breaking changes can increment the major version rather than staying in v0 which is harder to tell when a breaking change happens.
p.s. so far config changes in hyprland have only been a 5 min fix so i haven’t experienced this fuss yet, maybe soon!
Zed is the perfect example of that.
deleted by creator
Works fine for me:
Was my usercss acting up.