"Again, a bloody insult. You carefully choose words to insult the author, are you like that IRL as well?"

I'm not insulting the author, that is a statement about the article. If you are suggesting that everything you write has no flaws then I'm sure you understand how that's not a reasonable thing to say. I write plenty of stuff that has flaws. But I'm willing to field criticism and correct it if it's wrong, that's how we collaborate to make something that's twice as good because it combines both our knowledge. Please do not write these articles if you are not interested to field criticism, thanks. Also please avoid trying to second guess the technical direction of a project unless you are involved in its development in some way, otherwise more misinformation like this is very likely to occur.

"It's basically a virtual machine, almost like WSL for Windows. I couldn't care less about it because it's useful for packaging server applications, not for end users or ISVs."

I'm not sure I agree, I've seen many ISVs that ship docker containers, even for desktop apps. You may want to look more into this technology.

"Tell me how I can run KDE2/KDE3 applications in my Fedora 35 or Ubuntu 20.10. Your 'actually' is a MISINFORMATION when right now I cannot use most graphical applications just from 10 years ago."

Someone would have to package those applications for those systems. I could walk you through the process if you want help. It's not exactly an easy process and we will probably have to solve some issues but I think it's doable. The real problem here seems to be that those distros have stopped shipping those applications. Edit: Actually I think this would be perfect to do in a flatpak or snap, you really should consider asking someone to do that and making that more prominent in the article. I'd suggest that you avoid setting arbitrary time frames like "right now" or "in two weeks" or anything like that.

"Will not work, Qt2/Qt3/GTK1 are not available under new Linux distros in any shape or form. 'Too costly to maintain'. GTK2 will be removed soon. Linux proponents always like to talk about various 'workarounds' which are just NOT THERE for the average user. Docker is one of them."

So again that would be the real problem, those things are too costly to maintain and there is no manpower. All of that is true and you can just mention that in the article. Not sure what can be done about it, if you have some ideas I'd love to hear them.

"This is FALSE, period. Case in point: http://blogg.forteller.net/2016/humble-test/"

For whatever reason the spreadsheet doesn't load so I can't see what you're talking about or try to figure out what the problem is. But those are games so I doubt the problem has anything to do with X or Wayland or KDE or anything like that. It's possible it could be something simple, like a few missing libraries. But maybe not, I really don't know, and if you don't know either then I would suggest against saying that it's true or false. This is not something we can productively speculate about on a blog or social media, it needs to be investigated as an actual bug.

"Linux distros do not give a damn about any software which they don't include. They don't care about any forward or backward compatibility. Ubuntu just recently tried to remove all 32bit support only then they realized their Wine users would not appreciate it. Most don't care about any stability as they don't give you an option of using say e.g. the current stable kernel or LTS kernels. Period."

All of this is true but is again unrelated to the rest of the things you said. Please make the article more about this and what can be done about it, if you offer solutions on how to fix it that would be even better. Right now, the article offers very little in the way of constructive comments.

"Your 'solutions', 'workarounds', etc. are worth nothing if the average user who's going to install Fedora 35 in two weeks will not be able to use any of them. "

It would be nice if you could mention more examples of what this average user using Fedora is trying to do. It's not helpful to discuss theoretical users, a valid bug report needs concrete steps to determine what the problem actually is. I think that would also be a major problem with the article, most of the commentary is phrased as "X doesn't have Y" or "X doesn't let me do Y" when that's not really a meaningful thing to say in many cases. It's more helpful to phrase it as "I tried to do Y thing, the result was Z instead, here are the steps I took using software A B and C".