First thank you to all those who have read and commented ( both positive and critically ) on my article. All comments welcome. Having been a Slackware user for many years, the "Interview" series is my way of contributing back to the Slackware community - of course there is some bias involved here, but I still use a critical eye when going through the components I look for in a distro, so Slackware would not escape unscathed were I to find something wrong. Suffice it say as well that Slackware is not perfect, but it's close enough I think
PrinceCruise, you hit it on the head - my phrase "not half-bad" is intended as you might interpret the slang form of 'bad' - meaning good. I.o.w. I think Slackware makes a great desktop and have been using Slackware on my desktops for the last 8 years or so.
Regarding KDE issues that some have had, I don't regard code/release quality in KDE as something that Pat and crew can control, although they could choose to leave it out completely. Saying that, I've had a reasonably good experience with a number of Slackware/KDE installations. Most issues come about as a result of an upgrade of an existing installation ( and .kde profile ) or display driver issues. Removing your .kde folder and starting a fresh KDE profile ( yes I know it's a pain in the arse ) will most times solve any latent issues in a problematic KDE installation.
Regarding KWin crashes specifically, these can be caused by any number of problems ranging from display drivers to faulty user kde profiles and even hardware config/issues. Check your driver installation and start with a fresh profile on a new user, as above. You can even try disabling compositing if you don't need any fancy KWin features.
Regarding the article series itself, I'm starting to run into a lack of things to say after each successive release - each Slackware release is generally of high quality yet with a similar feel. Packages ( and therefore features ) are not typically added or removed at a high rate with each release so the results are incremental. And so the amount of stuff you can say about these releases becomes limited.
One thing I'm aiming for in future articles is to add more details about specific app/packages used in a server environment instead of just running through the feature set eg. I was intending to do some thorough testing on the new Apache 2.4.x/PHP 5.4.x with fpm layout ( a custom config that I failed to get working properly under Apache 2.2/PHP 5.3 ) for this latest article but I ran out of time. The LAMP stack is something I use a lot ( my most common apps are Joomla, Worpress, Mantis and OTRS ) so this kind of testing is valuable.
Thanks to all and happy Slacking!