

Thanks for posting the blogpost – when I checked this thread originally (and the article), I seemed to have missed the focus on DHH. Admittedly, I just don’t know much about him – though, I’m starting to get an idea why this blew up so much.


Thanks for posting the blogpost – when I checked this thread originally (and the article), I seemed to have missed the focus on DHH. Admittedly, I just don’t know much about him – though, I’m starting to get an idea why this blew up so much.


I’ll admit I’m not up to date on the hyprland/vaxry lore – but I don’t understand the level of outrage based on this article…
I’m also not sure why the sponsorship of a software project is necessarily being treated as a 100% endorsement of both the maintainers and their alleged views.
I’m also not sure if infighting and purity testing will help the movement(s) right now. Once it’s the norm, sure, but it’s still a relatively fringe movement within the industry.
Edit (2025-10-15@20:14): At the time of writing my comment, I was both unaware (and uninformed) on the DHH side of this topic. While I still think the level of outrage is maybe a melodramatic, the push back seems more warranted than it initially seemed to me. I still don’t know much about DHH beyond Rails (and even then, not much); but from what I’ve seen since my comment, the response is more understandable.


Doesn’t look nearly as verbose either


I’m still not convinced the engine is the problem. Maybe it’s not helping, sure, but heavy reliance on upscalers to achieve nominal performance is probably a bigger issue.
That, and shipping before proper optimization passes is probably more profitable in the short term, so publishers will push for that.


I’ve always used :sp & :vsp, though I’m not spending all day in a multi-split env.
From my experience, that sounds like an added bonus.