What do you think about these Ideas?

Thank you for taking the time to answer. In one point i disagree:
>> WordPress is not a CMS
IMHO it is 😉 as it stores all information in a db. Thats enough to meet my demandings to call it a CMS. Anyway, i know about all this, its flexibility and so on. But, don’t you think that there would be still a lot of work or optimization to be done to make Installation (with focus on hardcoding and editing files – especially localization) as intuitive as possible?
What are the problems from a technical point of view, that make a second install-screen, demanding for db-name, a db-pass and a dropdown list letting you choose your language impossible? imho wp is user-friendly already, but improving can be done.

To finish with a drastic Question: Why not establish higher requirements or standards to anything that is (or becomes by adding) a part of wp, such as plugins, themes etc.? So why not throw all such things out of the Repository if it doesn’t meet a certain quality-standard (eg if only one word of a specific language shows up in it, code isn’t semantic or there are things left unstyled – what btw, would force me to rework my theme, too).
I’m focussing on language here, because i think thats an area where the most can be improved, taking a look at the awesome Giraffe-Theme, i learned that this isn’t impossible to deal with, so why not include all language files in a way (maybe an automated download of someones selection in the background) into the wp-install, in order to avoid the necessity to do poEditing.
any other ideas in general, what are other beginners struggling with?

shipped plugins: i disagree here. this is one of the best parts in wordpress.

i agree, maybe i wasnt clear enough, i’m looking at some really essential things (at least for me) when saying “include more plugins”.
I know WP isn’t neither written for Germans in the first place but, take German Umlauts (ÄäÜüÖö) for example: What is ok with permalinks in Francais or Espagnol has not necessarily to be right in other languages. An “é” with accent tégu leads to a url (and permalink) with just an “e” in it, what is fine, but in german language an “Ãœ” should be transformed into “Ue” (München -> Muenchen) instead.
An optimised language support, asking me on the first Install-Screen what my native language is and does the rest on its own, would help a lot to eliminate fears regarding tech-things with beginners.
Instead they read their first Error-Messages in plain English (if theres no database 😉 for example), so am i right that WP is written for English-Speakers in the first place? dont think so…
So if wordpress knows, that im german, it wouldnt confront me with english error-msgs or tips at any time and wp then should know that i want “ue”s instead of “u”s and keep me from manually doing the currently necessary steps:
1) install english wp
2) download de.mo (which i might have to rename into de_DE.mo in some cases. why? That i have to search for this file in the codex first, what i will, of course, only do when i know that this feature exists – no word on that during the installation, like in every other common windows-software installation)
3) Create a special language-subfolder (that shall imho already exist)
4) edit the wp-config.php again (why not a dropdown in admin if i want to change language back to whatsoever-language on the fly?)
5) find wp-umlauts plugin
6) install it, activate it
and still find a blog that isnt completely in my preferred language (not to talk about plugins…)

kindly, erik
ps: kjell, sorry i dont get you. What you mean with “hidden” advantages? what wp-part or process are you driving at?