Here's my attempt at a summary (likely biased, not complete, with mistakes).
Basically, aside the mentions of bugs and the hatred against Wayland, the author dislikes the trend everywhere to hide buttons behind menus in the name of a better organization, requiring more clicks to get things done, and to dumb down UIs for idiot mainstream users. The KDE dev disagrees with this premise, thinks that additional clicks don't matter much in the grand scheme of things, but making things more organized and less cluttered is a big win for making things easier for first time users while not alienating expert users that much, and rejects the idea that we should consider mainstream users idiots.
More specifically:
- KDE dev is happy this is a critical review: they are rare, usually reviews are just uncritical tours of new features which are not helpful feedback. He encourages the author and other people to keep doing this.
- Wayland vs X11 perf: surprising results, usually Wayland benchmarks are better
- The KDE dev doesn't see the differences wrt to font rendering from the screenshots but says we shouldn't trust him on this. Qt should be handling font scaling well. Again, this part is usually better on Wayland
- the 105% scaling could be a result of the complex logic that tries to figure out the correct scaling for your hardware (I agree with the blog post that 105% doesn't look good. Now, nothing prevents from reporting a bug)
- data shows that complaints from users are fewer with Wayland than with X11
- the gamma complaint is one of the niche issues that indeed Wayland doesn't address, but that doesn't mean Wayland is a big mess
- the blog post complains about Scrot, a screenshotting tool, not working on Wayland and that it's the kind of basic features Wayland messes up. It's false, on the contrary, it is a side effect of what Wayland tries to address (security), Wayland provides features to do screenshots, Scrot needs to adapt.
- blog complains about lack of borders, but KDE has been moving away from them to reduce clutter
- KDE dev says he actually likes the Gnome 3 / Windows 11 UIs
- KDE dev defends the idea that more clicks is sometimes better (if it allows better and clearer UI organisation), and can help provide more features, and can help new users figure things out by reducing the number of things appearing on the screen which is also important
- KDE dev rejects each suggestion to add buttons to the Dolphin toolbar (refresh: shouldn't be needed, Dolphin already autorefreshes; Home is already in Places, cut, copy and paste can be found on the context menu which is where users will look for these actions). He mentions that people not liking the hamburger menus are at a CTRL+M away from enabling back the regular menu.
- KDE dev says Spectacle is as efficient as possible like this, and doesn't get the complaint (as someone who followed Nate's blog posts, I followed evolutions of Spectacle, I do believe it indeed improved a lot over the time). He says that Plasma is often rightfully criticized for being overwhelming and they are trying to fix this
- KDE dev rejects the idea that we should consider the vast majority of users as idiots, but as people whose life doesn't revolve around computers and doesn't think that the improvements puts unreasonable burden on expert users (and as someone who has used KDE virtually forever, I agree)
- KDE dev says that saying Spectacle's UI being ruined is overly dramatic
- KDE dev is the one who designed the floating panel and feels being called out. He says that the floating panel was done to stand out from other desktop in screenshots, especially Windows. He says that expressly they made sure pushing the cursor to edges and corners work and added an option to revert the floating panel anyway. He says that the blog author should have tried and gets angry at the "malicious" accusation that the floating panel is there because Qt6 provided a shiny new widget that absolutely had to be used.
- KDE dev takes looking like Gnome 3 as a compliment because they have good designers
- KDE dev rejects the idea that displaying all the detailed packages to updates in a system upgrade is a good idea for the majority of users (everybody does this, it would be overwhelming)
- KDE dev argues in favor of robust, reliable system upgrades and rollbacks, also explains the advantages offline updates and how updates while the OS is running can break stuff because you end up with a system running mixed versions.
- KDE dev recognizes KDE Neon can have issues
The conclusion is a rehash of all this. He reaffirms that they are trying to build good software, not mimicking cheap competition. He rejects the idea that efforts working on atomicity and Wayland would have been better directed at improvements because they bring improvements. He rejects the comparison with Chromebooks, which are SaaS, while KDE remains local.
The KDE dev disagrees with this premise, thinks that additional clicks don't matter much in the grand scheme of things,
I wonder how much that dev would care if someone changed the workflow of their favorite C++ IDE setup to constantly require multiple extra clicks/steps to perform common activities.
The problem is not so much about "more mouse clicks". The problem is that by forcing the use of an hamburguer menu, you *must* use a mouse.
In a traditional WIMP GUI app, you press Alt and automatically there is a letter in the menu underlined. That means that pressing that letter in the keyboard, you get the menu pulled down. Then, you can navigate it using cursor keys + enter or other highlighted letters.
This is no longer possible with most hamburguer menu apps in Plasma. You MUST use the pointer device (mouse). That is my pet peeve. More or less clicks is not really of the essence.
Basically, aside the mentions of bugs and the hatred against Wayland, the author dislikes the trend everywhere to hide buttons behind menus in the name of a better organization, requiring more clicks to get things done, and to dumb down UIs for idiot mainstream users. The KDE dev disagrees with this premise, thinks that additional clicks don't matter much in the grand scheme of things, but making things more organized and less cluttered is a big win for making things easier for first time users while not alienating expert users that much, and rejects the idea that we should consider mainstream users idiots.
More specifically:
- KDE dev is happy this is a critical review: they are rare, usually reviews are just uncritical tours of new features which are not helpful feedback. He encourages the author and other people to keep doing this.
- Wayland vs X11 perf: surprising results, usually Wayland benchmarks are better
- The KDE dev doesn't see the differences wrt to font rendering from the screenshots but says we shouldn't trust him on this. Qt should be handling font scaling well. Again, this part is usually better on Wayland
- the 105% scaling could be a result of the complex logic that tries to figure out the correct scaling for your hardware (I agree with the blog post that 105% doesn't look good. Now, nothing prevents from reporting a bug)
- data shows that complaints from users are fewer with Wayland than with X11
- the gamma complaint is one of the niche issues that indeed Wayland doesn't address, but that doesn't mean Wayland is a big mess
- the blog post complains about Scrot, a screenshotting tool, not working on Wayland and that it's the kind of basic features Wayland messes up. It's false, on the contrary, it is a side effect of what Wayland tries to address (security), Wayland provides features to do screenshots, Scrot needs to adapt.
- blog complains about lack of borders, but KDE has been moving away from them to reduce clutter
- KDE dev says he actually likes the Gnome 3 / Windows 11 UIs
- KDE dev defends the idea that more clicks is sometimes better (if it allows better and clearer UI organisation), and can help provide more features, and can help new users figure things out by reducing the number of things appearing on the screen which is also important
- KDE dev rejects each suggestion to add buttons to the Dolphin toolbar (refresh: shouldn't be needed, Dolphin already autorefreshes; Home is already in Places, cut, copy and paste can be found on the context menu which is where users will look for these actions). He mentions that people not liking the hamburger menus are at a CTRL+M away from enabling back the regular menu.
- KDE dev says Spectacle is as efficient as possible like this, and doesn't get the complaint (as someone who followed Nate's blog posts, I followed evolutions of Spectacle, I do believe it indeed improved a lot over the time). He says that Plasma is often rightfully criticized for being overwhelming and they are trying to fix this
- KDE dev rejects the idea that we should consider the vast majority of users as idiots, but as people whose life doesn't revolve around computers and doesn't think that the improvements puts unreasonable burden on expert users (and as someone who has used KDE virtually forever, I agree)
- KDE dev says that saying Spectacle's UI being ruined is overly dramatic
- KDE dev is the one who designed the floating panel and feels being called out. He says that the floating panel was done to stand out from other desktop in screenshots, especially Windows. He says that expressly they made sure pushing the cursor to edges and corners work and added an option to revert the floating panel anyway. He says that the blog author should have tried and gets angry at the "malicious" accusation that the floating panel is there because Qt6 provided a shiny new widget that absolutely had to be used.
- KDE dev takes looking like Gnome 3 as a compliment because they have good designers
- KDE dev rejects the idea that displaying all the detailed packages to updates in a system upgrade is a good idea for the majority of users (everybody does this, it would be overwhelming)
- KDE dev argues in favor of robust, reliable system upgrades and rollbacks, also explains the advantages offline updates and how updates while the OS is running can break stuff because you end up with a system running mixed versions.
- KDE dev recognizes KDE Neon can have issues
The conclusion is a rehash of all this. He reaffirms that they are trying to build good software, not mimicking cheap competition. He rejects the idea that efforts working on atomicity and Wayland would have been better directed at improvements because they bring improvements. He rejects the comparison with Chromebooks, which are SaaS, while KDE remains local.