The main problem is [...]
I'll admit, I only vaguely know of DHH by name and Rails, vaguely remember the Omarchy announcement, and that's about it. I seem to recall Prime referencing DHH's controversial opinions, but I can't say I've gone any deeper than that.
If the discourse really is primarily focused on DHH/Omarchy, then I guess I just misunderstood this post/title & the article...or just don't have the full context regardless.
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.
Huh, I hadn't realized you could chain -exec statements in this way; I assumed \; or {} + had to be the end of the arguments.
Maybe including something like Windows' OOBE; rather than defining a user before installing?
My last svn interaction was last week -- boss is committed to sticking with subversion until the end of time.
This may also come down to hardware support generally; we ran into an issue upgrading an OS from CentOS 7 to Rocky 9; where RH had dropped support for our hardware during the RHEL 8 releases.
Debian, on the other hand, still had drivers available.
It was fun enough to play through early into EA; though once I started to scale up for a MAM, the performance became untenable... Though, that's what you get for EA I guess.
Guess I was a little confused; at least their repo, change log and project website still point to Mozilla (in droidify, anyway).
As I added in another comment, I misunderstood the DHH element of the discourse as I, admittedly, don't know much of anything about him -- I've heard some references here and there, but that's about it.
That's also fine, and I generally agree. My concern basically boils down to killing momentum by sinking a company with (probably?) sane views on right-to-repair & libre as topics.
If the goal of a boycott is to starve the company until it goes under, because they made a move we don't like -- then that I don't really like in this context. If the goal is to force their hand towards at least transparency, or maybe force NP to step down; then I'd support that.