Slashdot Mirror
Testing the KDE 4.2 Release Candidate, On Windows
Verunks writes "Ars takes the KDE 4.2 release candidate out for a test drive on Windows. The popular open source desktop environment has moved beyond Linux and is becoming increasingly robust on other platforms. Even KDE's Plasma desktop shell is now Windows-compatible."
Congratulations on your purchase of a brand new nigger! If handled properly, your apeman will give years of valuable, if reluctant, service.
INSTALLING YOUR NIGGER.
You should install your nigger differently according to whether you have purchased the field or house model. Field niggers work best in a serial configuration, i.e. chained together. Chain your nigger to another nigger immediately after unpacking it, and don't even think about taking that chain off, ever. Many niggers start singing as soon as you put a chain on them. This habit can usually be thrashed out of them if nipped in the bud. House niggers work best as standalone units, but should be hobbled or hamstrung to prevent attempts at escape. At this stage, your nigger can also be given a name. Most owners use the same names over and over, since niggers become confused by too much data. Rufus, Rastus, Remus, Toby, Carslisle, Carlton, Hey-You!-Yes-you!, Yeller, Blackstar, and Sambo are all effective names for your new buck nigger. If your nigger is a ho, it should be called Latrelle, L'Tanya, or Jemima. Some owners call their nigger hoes Latrine for a joke. Pearl, Blossom, and Ivory are also righteous names for nigger hoes. These names go straight over your nigger's head, by the way.
CONFIGURING YOUR NIGGER
Owing to a design error, your nigger comes equipped with a tongue and vocal chords. Most niggers can master only a few basic human phrases with this apparatus - "muh dick" being the most popular. However, others make barking, yelping, yapping noises and appear to be in some pain, so you should probably call a vet and have him remove your nigger's tongue. Once de-tongued your nigger will be a lot happier - at least, you won't hear it complaining anywhere near as much. Niggers have nothing interesting to say, anyway. Many owners also castrate their niggers for health reasons (yours, mine, and that of women, not the nigger's). This is strongly recommended, and frankly, it's a mystery why this is not done on the boat
HOUSING YOUR NIGGER.
Your nigger can be accommodated in cages with stout iron bars. Make sure, however, that the bars are wide enough to push pieces of nigger food through. The rule of thumb is, four niggers per square yard of cage. So a fifteen foot by thirty foot nigger cage can accommodate two hundred niggers. You can site a nigger cage anywhere, even on soft ground. Don't worry about your nigger fashioning makeshift shovels out of odd pieces of wood and digging an escape tunnel under the bars of the cage. Niggers never invented the shovel before and they're not about to now. In any case, your nigger is certainly too lazy to attempt escape. As long as the free food holds out, your nigger is living better than it did in Africa, so it will stay put. Buck niggers and hoe niggers can be safely accommodated in the same cage, as bucks never attempt sex with black hoes.
FEEDING YOUR NIGGER.
Your Nigger likes fried chicken, corn bread, and watermelon. You should therefore give it none of these things because its lazy ass almost certainly doesn't deserve it. Instead, feed it on porridge with salt, and creek water. Your nigger will supplement its diet with whatever it finds in the fields, other niggers, etc. Experienced nigger owners sometimes push watermelon slices through the bars of the nigger cage at the end of the day as a treat, but only if all niggers have worked well and nothing has been stolen that day. Mike of the Old Ranch Plantation reports that this last one is a killer, since all niggers steal something almost every single day of their lives. He reports he doesn't have to spend much on free watermelon for his niggers as a result. You should never allow your nigger meal breaks while at work, since if it stops work for more than ten minutes it will need to be retrained. You would be surprised how long it takes to teach a nigger to pick cotton. You really would. Coffee beans? Don't ask. You have no idea.
MAKING YOUR NIGGER WORK.
Niggers are very, very averse to work of any kind. The nigger's most
The only Kike Development Environment I want to see is a gas chamber.
There shouldn't be bug report for this category of obvious flaws. If you had one look on the desktop you would have seen it.
But no, it is way more cool to add another KAdapter/KProtocol/KDecorator than simply making the whole thing useable.
You and your cabal are what's wrong with KDE development. You.
Portability was one of the goals of KDE4, and it is encouraging to see it works.
Now if only the other parts of it would stop sucking...
How about making it stop sucking before making it portable?
If you want an example as to why you should prioritize this way, look at the popularity of NetBSD.
Today's Daily KDE4 WTF: My clock has two lines. The first line is the time, in military time -- 08:31. This works fine. The second line is the date: Tue, 27 Jan. It might be 27 January, but I can't tell, because the T and half the u in Tue, and most of the n in Jan, are cut off.
Then there's the Gnomification / castration of configuration options.
If someone is passing you on the right, you are an asshole for driving in the wrong lane.
There shouldn't be bug report for this category of obvious flaws. If you had one look on the desktop you would have seen it.
Fallacy. If we had one look at the OP's desktop then we would have seen it. Unfortunately, the users who test KDE cannot possibly test every permutation of hardware that exists that supports KDE. It's simply impossible. However, I'm willing to bet that the machines they did test on did not exhibit this problem. Hence, they never knew a problem existed.
So... the bug report will be marked "Cannot reproduce". Then a couple other suckers that were so annoyed by it that they took the time to create an account in the bug system will post "Still reproducible on 4.4", but it'll never get fixed. And even if it does get fixed, the bug report will never be changed from "Cannot reproduce" to "Fixed" since it's lost in the morass. The people who filed and posted 'me too' and the people that read the report and didn't register will all be even more pissed off.
Testing and bug tracking does not work well when the underlying code is really buggy. Quality of a program should be judged by its worst part... it's better to have good quality throughout than to have some perfect code mixed in with some really bad code. IOW, there shouldn't be problems with just a couple fields being a couple pixels off like that.