FreeBSD's Handbook is available in Japanese and German, if you like. KDE has been localized to those same languages. We can help you put it all together, just ask here at the Forums, and we can point you to the Handbook, and even help with connecting the dots.
It does help to remember, FreeBSD and KDE are separate projects.
That is not sarcasm. That is what Deutsche Telecom told to Steve. And they wanted the browser to hardwire the home button to their home page. Steve gave them the 132 answer.
Yes, but MacOS is also a commercial OS. Which in this case I think is a fairly significant consideration. It is used by people paying to have everything done for them.
You barely have to learn how to get X working to just type a few simple pkg commands. If they are "too busy" for that with their high flying life, then how do they expect to be able to install development / networking tools you mentioned they might be interested in?
Ultimately that is an opinion. My opinion is that I actively choose to use the command line, just to avoid Apple's naff awkward interface. Opinions are effectively worthless but unfortunately computing environments aren't easily something that can be measured.
Here's a serious suggestion - you wouldn't need to create yet another DE or WM, just write a theme pack that customizes the main ones being used, then make it as a port. For example, I use primarily XFCE, and sometimes KDE. I almost always replace the little mouse or the "K" in the "start" buttons with a FreeBSD logo. Just a nice little touch that makes this instantly recognizable for not being just another OSS Desktop system. Someone with some more artistic flair and patience for making themes could easily create a theme pack that would give some consistency across the various DEs. Then you just have to advertise it for people to use, promote it, etc.
I'd rather not add yet another port to an already rather unwieldy collection. We have truckloads of language modules as ports (Perl, Ruby, PHP, etc). Those themes should be installable to $HOME, and available through the DE's channels, rather than crowding the Ports at FreeBSD. Just my opinion here. ?
Perfect analogy.
Some Lego kits do come pre-built in the box if you shop around. But those are a pain to get out of the box, and the one I linked to is $680 USD. I like to compare FreeBSD to cooking - Just try combining regular flour, yeast, water/milk, eggs, salt and sugar for a good texture. Temperature makes a difference, so do relative amounts, the possibilities are endless with just those raw ingredients. FreeBSD is the farm for just a few high quality ingredients, not a cooking research school.
Hmm, that sounds familiar. See #3 here:
judecnelson.blogspot.com
Nice straw man you got there.
1. I get X working, but it is never a "few simple pkg commands." Having to memorize, look up, or disassemble to read the model on whatever video card you have in your system in order to pkg install the correct driver when the computer is capable of just telling you via PCI ids is frankly ridiculous.
Yes it is.
No you don't
No it's not. I reinstalled everything a few months ago and it took me maybe 20 minutes including all the software packages I use daily. Far better than Linux where it installs too many things I don't want and have to uninstall them, find out that broke something, leaves unused packages behind, corrupts the OS and I have to reinstall all over again, possibly repeating the same thing.
I believe the only awkward one where you need to do that here is Nvidia because it is a proprietary (and out of kernel) blob. But I am not entirely sure that is any different whether installing the driver for Windows or Linux.
Windows detects and downloads the correct driver at least to get a framebuffer working, if not modest acceleration. I don't know what linux does.
Yeah, so is peeling your own potatoes before boiling them with a bit of salt. You want a bag of potato chips instead, and not risk cutting your fingers while peeling the potatoes (which also need to be washed/rinsed beforehand). ?
In the same way that vesa or scfb is always available from the xorg meta package. In all cases a user will still need to manually install the actual correct driver for power management (suspend / resume, brightness on laptops, etc), wider range of native resolutions and 2D/3D acceleration.
