I did not say "despite having a fix to hyprland, they don't offer a standalone recipe", I'm referring to the whole behavior: how it is presented, how it is hyped, how there is its own conference, its own merchandising, ... When it comes to hyprland, there is this childish attitude of "people do what they want, extract it from the source yourself" when people are legitimately surprised on how the thing was handled.
If it was presented as "Hey, we know it's just some scripts, we don't do the same kind of work that traditional distributions do. We still call it a distribution, but don't hesitate to support Arch instead who is doing the hard work for us", it would be different. But it is apparently not what is done (based on what I've read on the subject in the meanwhile).
What I'm saying is obviously not as simplistic as how you summarized it. It looks like you are just upset that someone may see bad signs in the way this distribution (or whatever one wants to call it) is handled. That's fine, I'm not forcing you to not use it, the same way I'm not forcing anyone to not use anything that is overhyped.
> I did not say "despite having a fix to hyprland, they don't offer a standalone recipe",
You said this:
> Did dhh provide a recipe to install hyprland properly without having to install a full "distribution"? (I don't know, it's a real question)
> It feels very strange (and wrong) to me: if there is difficulties in installing something, try to help people instead of packaging the solution with other things that are not related.
And this:
> If indeed dhh helped find a way to install hyprland more easily but failed to also provide a standalone recipe, that does not sound like a good practice to me.
I understand your overall point now that you took the time to explain a bit more, and it is valid criticism. But it is not "obvious" what you were saying. Based on the replies you've got, I see that I'm not alone to think this. You might want to look inward into why that is.
Not upset by the way, just responding in kind.