To add to what you said: Some parts are useful on its own. Don't need targets, having a list of Linux issues is helpful enough. If you're involved in a project

To add to what you said: Some parts are useful on its own. Don't need targets, having a list of Linux issues is helpful enough. If you're involved in a project you can pickup bits and take it from there. But that's combined with a lot of offputting content. E.g. the need to say everything is correct because Slashdot agrees and saying/suggesting Slashdot is unbiased and representative. Swearing at the developers who actually put in work (disagree heavily all you want, but no need to swear). Same for saying/suggesting that some developers don't mean well. Initially I only read the first part and thought it quite improved from the last time I read it. But no, again the argumentative stop energy. :-( Further, a few of his issues are just opinions. Why combine that with the others? Someone else said here: "he's right". Unfortunately not and again I already regret reading the various drivel parts.