Apple does it more sparingly (now), and fairly consistently: as a product line evolved. The iMac line did it when it was "cool", the iPod was the next one, and the iPhone evolved from the iPod so it made a lot of sense (and thus so did iOS). There's not really anything else Apple names this way. Apple TV, Macbook, Airpods, Safari... Whereas with KDE everything has got to have a K, it's pretty ridiculous. It's also not a particularly "pretty" letter and you end up with names that are either purposeful misspellings, midKapitalized, are plain bad puns, or occasionally and at best, are merely oKay.
KDE does not have a great brand. Apple does.
It might also be interesting to note that Apple licenses iOS from Cisco [0].
[0] https://appleinsider.com/articles/10/06/08/cisco_licenses_io...
Also, Apple no longer has iLife or iTunes, and "iWork" is no longer a bundle, but even if it was, its apps are Pages, Keynote and Numbers. No "i"s there.
They use the "i" prefix more sparingly now, as the original post said.
I've never heard of iLife, iTools, iWeb, iWork or iSight so its use in flagship products is even more sensibly sparing.
iTunes has been replaced by Apple Music, and possibly iMovie too???
It's also worth noting Apple has been somewhat mocked got their overuse of i. Despite the sparing use. So KDE tacking it onto everything is even less sensible in this context.
I think the K naming has probably hampered adoption of KDE products in the long term: I was always resistant to install K* apps when I was using a non-KDE desktop due to compatibility paranoia, something I tended not to even consider when installing gnome/gtk apps for example (which tend mostly not to be prefixed with g or gtk- or similar)
The i-branding was very, very effective. Apple was one of the very few brands that really managed to "own" the internet in the mind of the average consumer. Which is one of the reasons it was wildly successful.
The new branding, in comparison, is meh. They now just leverage "Apple". Nothing else, because they think they are too good. Creating new brands is difficult and risky, so they just don't do it because "we don't need it".
It's a sign of decadence, and you can see it in the history of all corporate behemoths. Once Microsoft became huge, everything became "Microsoft This" or "Windows That" - they stopped making bets, and just leveraged their established brands. The rebirth was a fountain of fresh brands: Azure, Surface, Office365.
"Apple Music" and "Apple TV" are one of the many symptoms of a culturally-dying corporation. Like Microsoft, they will continue to be fabulously rich for decades, maybe score the occasional win like the move to ARM. But the new booms will come from elsewhere.
Neither is what KDE are doing with their persistent k* prefix: it's not decadent nor innovative. It's just stagnant.
Not really. The main desktop/interface, i.e. that users spend most time looking at, is called Plasma. The file manager, another high-usage application, is called Dolphin. The theme is Oxygen/Breeze.
Claiming 'everything has got to have a K' is about a decade out of date. Sure there are still things like KClock, KRunner, KWin, etc. but they mostly seem to be very old projects, from back when 'everything has got to have a K'. Others, like Konqueror, Kontact, etc. seem like pretty reasonable names.
No longer true. But nobody wants to rename well known apps like Konsole to Terminal , Kate to "Text Editor".
According to Wikipedia, however there is no citation.
https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Ia...
The one thing that keeps me in the *nix universe is the ability to pick and choose my desired software (and hardware ofc) without being influenced by iMarketing. I really dont care if KDE has a poor brand as long as it does its job well.
In this case. The more users and interest in KDE/Plasma, the better for the whole environment and the developers.
(Sorry couldn't resist, I know many apps just have a normal name with a K prepended.)
That said, some/any name is vastly preferable to just "camera". If you have a question about the app how are you supposed to google for that? You start searching for "apple camera app" at which point that might as well be its name.
Anyway, the Keverything is a copy of the Xeverything, and both are for practical reasons since they point to the requirements to run the software.
Also, the original comment did not say anything about Apple. Stop trolling.
Knames are mostly ok, a user knows right from package list if this app is meant for his environment, or rather not. Same with gApps. The name tells what the app does. Why would I be mad at this?
They have some great pieces of software but marketing wise it looks like they don't want to go beyond their Kusers.
This is my opinion anyway.
It's not at all hard to pronounce. It's my second language yet still spelling and clock was things I was taught in kindergarten. There was also this weird cartoon [1] about green monster eating clocks.
Make some proposals.
It's surprisingly hard to find actual packet/binary name of the app while actually using it. Modern Linux apps love to hide it, good luck if you use a proper translation. Everything is called "Editor" or "file manager" etc.. I have to use "ps" to figure that out.
"how do I do X with Nautilus/Epiphany/Totem"
In the associated articles you can see the user-facing name for kclock is "Clock": https://www.plasma-mobile.org/2021/06/10/plasma-mobile-updat...
Probably it's just me, though: at that time I was working at a company with a name starting by V. The product name itself also started by V. We used the C++ Qt framework, where every class starts with Q. So the lead devs picked up the trend and all our classes' names also started with V. Basically everything was named as something following the same letter.
That can be usefull, you know by looking at a class name , if it starts with Q is a native Qt stuff, and if it starts with V is your own custom stuff. As an example if you would see a VDropDown you will know that some of the developer in the company was asked to "improve" the native dropdown , you should check if there are bugs there.
However I don't think it's a good idea, nor pretty or attractive, that such a technical decision transpires to the public facing side of the project: first and foremost, its name.