Comment Grifter says a thing (Score 2) 160
Comment Why does it have to be Flock or nothing (Score 2) 90
Comment Re:What's new here? (Score 1) 57
Comment Re:What's new here? (Score 1) 57
Comment Re:"could" (Score 1) 159
Comment "could" (Score 3, Interesting) 159
Comment Re: Too expensive (Score 2) 56
Comment AI & PMCs s make handy scapegoats (Score 1) 286
Comment Too expensive (Score 2) 56
Google also hasn't helped itself by having ChromeOS *and* Android and trying to mush them together so badly. I have no idea if "Googlebook" is where the two finally become the one, or not, but the company must have wasted hundreds of millions in development, customer confusion / dissatisfaction by having this disconnect.
Comment Re: Nothing of value was added (Score 1) 162
Comment Re: Nothing of value was added (Score 1) 162
Comment Still that kitchen sink mentality (Score 2) 82
And when you read KDE's human interface guidelines it becomes clear why it's such a mess. The HIG reads like a developer free-for-all. It points at existing apps as precedent, or mentions some class or another, or waffles into wordy sections. But what it doesn't do is layout a clear vision of what KDE UX should be including illustrative examples, usage patterns and so forth. Some of the HIG is hilariously stupid, such as explicitly refusing concepts like basic & advanced settings. No wonder its a kitchen sink.
Compare to the GNOME HIG if you want to see what a HIG should be. And no that doesn't mean KDE needs to "dumb down" to become GNOME but it needs to lay out its stall in a way that developers can follow and its UX needs to be designed on sound principles. e.g. KDE has Kirigami to produce modern usage patterns, so write the HIG around that. Make it fit for purpose and maybe some of that kitchen sink mentality will go away.