The title's a bit of a joke and this is perhaps not appropriate to meta but I'm throwing it in (shoot me).
I just spend several hours (most of the morning, actually) adding to this answer on a closed question (the addition starts with [Post OP Revision], -- make sure to scroll down because the first part is not relevant). I'm not debating the closed status (I voted that way). However, it's a particular kind of question where I'm always wishing I had some external resource to refer to,1 but have never seen anything that comes sufficiently close to what I'd like to say, and what I'd like to say is just too much to pack into an answer particularly since these kinds of questions are opinion based and should be discouraged.
So occasionally I go ahead and do it anyway on the premise that one day in the future I'm going to gather that material together (hopefully these aren't deleted, lol) and put it online and then I will have an external reference,2 and will hopefully never again have to spend hours trying to explain all this, because I have a polished, canonical version of my own thoughts on the matter.
That resource would would be, in part, an explication of the modular and heterogeneous nature of linux and linux distributions, which is something I've worked on in other questions and is a relatively concrete, objective topic. All by itself, however, I don't think that is sufficient, and the answer I've referred to here is perhaps the other half of the picture.
I'm looking for some feedback, first and foremost WRT inaccuracies (i.e., if you have time, read through and point them out). But TBH I don't think there's much of that. What I'm also looking for is opinions with regard to what is most contentious.3 The reason for that is I do NOT want to write a manifesto, meaning I don't want it to be about what I think the "linux world" should be ideally, I want it to be about what it actually is (and what it is not). Finally, I think a lot of people will be copacetic and positive feedback and suggestions/references4 from the like-minded would be terrific.
I'm asking here partially because the original question is closed and should remain so, and perhaps there is something that can come out of this providing a benefit to U&L.
1. As in, "Go read this if you want to understand what's wrong with your question."
2. I know slm already does this albeit with more technical material, which I think is great.
3. Contentious perhaps because they are not usually framed explicitly? I'm thinking of stuff like (with emphasis added):
"distros which parallel Redhat tend to be behind the times by a year or so [...] sort of pointless [...] in the context of a single computer owned and operated by you for you, any problems resulting from not standing back far enough from the present are probably easily rectified"
"Contemporary linux is what it is and two of the things I consider shining traits -- heterogeneity and transparency -- have a side effect, namely, it takes a much greater degree of technical proficiency to use effectively than say, OSX."
"unlike with commercial products, the authors of the software may not have much incentive to get you to use or understand it. If you have problems using it, there's no reason it should matter to them at all."
"it is easy to regard the system from an end user perspective as essentially the same kind of thing as a proprietary OS. This is a mistake, not because I think you need to care about FOSS ideology, but because there are some substantial pragmatic differences..."
"As a linux user, YOU are part of the project to a much greater extent than the average user of the big proprietary OS's [...not] because I think that a sense of community is a nice thing [...but] because the project requires work and you need to see yourself as part of that work (rather than as a consumer of it) [...] pragmatically speaking."
"Switching distros out of frustration is giving up; I've done it, and in the long run I don't think it accomplishes much beyond soothing the momentary anger [...] Eventually you have to sit down and accept that if you want something your way you may have to do it yourself."
4. Eric S. Raymond springs to mind, although TBH I haven't actually read the book.