I don’t think they’re saying they know better. Seems more like they’re tired of pouring hundreds of hours of free labor specifically into accessibility only to hear people bitch about how they’re not doing enough when the people bitching probably don’t even genuinely care beyond using it as a way to bash GNOME.
To which your response is to take the opportunity to talk shit about GNOME and disregard his meaning, which kinda illustrates his point.
Having learned Nix recently and still not being great at it, writing your personal config is relatively easy. The website has a search feature for options you can use by default, so it’s pretty straightforward. Just search for relevant keywords and set the options you like.
If you want to package software for nixpkgs, define custom options, or anything else that’s going to require custom Nix, it’s… Better than you make it sound but not great. I only read one guide, and it wasn’t great, but it covered the basics well enough. From there, I managed to figure out what I’ve needed so far just from the official documentation for the Nix language. It’s not everything it could be, but it’s not too bad.
If you wanna really get into the thick of it and extensively write Nix for some detailed purpose, you might run into some more problems. I still don’t think it’d be as bad as you make it sound, but you probably won’t be thrilled, either.
There’s work being done on it, but from my understanding, it’s slow going…
Using something like PeerTube is potentially even worse because let’s say you unknowingly open a video where someone in it looks of age but technically isn’t. You as a user help propagate that content while you have it open. You’re not just downloading illegal content at that point. You’re actively sharing it to new people.