And that is why I no longer use Hyprland and actually thinking about removing that branch from my dotfiles repo. Why vaxry doesn’t seem to understand the concept of “deprecation”?
I moved on to Niri a couple of months ago for various reasons, constantly having to fix and re-check my config against the docs being one of them.
For me Niri performs better, I really like the workflow and the dev behind it is very deliberate with new features and changes. Feels like he has a clear vision on how it’s supposed to work and it shows imo.
Just recently switched to Niri myself - I think the fact that Niri inherits a lot from Smithay for compositior stuff really helps. It’s the same compositor base that cosmic DE uses. Sure hyprland has HDR at present and Niri doesn’t, but I think it helps a lot to not build a compositor and a TWM at the same time. vaxry is honestly just doing way too much and it’s unsustainable and new version blow ups like this were inevitable given how big the install base has become and how huge hyprland feature set has gotten
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!
And that is why I no longer use Hyprland and actually thinking about removing that branch from my dotfiles repo. Why vaxry doesn’t seem to understand the concept of “deprecation”?
I moved on to Niri a couple of months ago for various reasons, constantly having to fix and re-check my config against the docs being one of them.
For me Niri performs better, I really like the workflow and the dev behind it is very deliberate with new features and changes. Feels like he has a clear vision on how it’s supposed to work and it shows imo.
Just recently switched to Niri myself - I think the fact that Niri inherits a lot from Smithay for compositior stuff really helps. It’s the same compositor base that cosmic DE uses. Sure hyprland has HDR at present and Niri doesn’t, but I think it helps a lot to not build a compositor and a TWM at the same time. vaxry is honestly just doing way too much and it’s unsustainable and new version blow ups like this were inevitable given how big the install base has become and how huge hyprland feature set has gotten
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.
It really is a problem. I don’t think I ever used another WM that broke config as much as Hyprland.
hyprland moto should be: the faster one moves, the harder it will crash onto the wall, and we are at C speed
You don’t have to tell me master. That shit broke more than my Arch install.