> How can a user do the work of not breaking something! Only the developers can do that.
You do realize that KDE4 is a completely new platform, right? New ideas, new architecture, new APIs. It's not just some random modifications to KDE3.5. Everything in KDE4 was written for KDE4, either from scratch or as a port from KDE3.5. None of that happens by itself. They didn't "break" the X.509 certificate support; they wrote a new browser which happens to resemble the KDE3.5 browser superficially, and haven't gotten around to implementing that feature (since very few people need it).
> Me, I thought that konqueror was indeed one of the killer features of KDE back in the day.
Perhaps it was, once, but it's been declining ever since Firefox became popular as a free, cross-platform alternative, long before it was reimplemented for KDE4. It was never much more than a thin front-end for KHTML, compatible with the rare minority of pages which are actually standards-compliant, written in the days when it was considered cool to merge web browsers and file managers into the same package. Nowadays KHTML is called WebKit, and the primary open-source front-end is Chromium. Why bother maintaining a second one?
You're welcome to continue using KDE3.5. There's even a fork already started to continue development on the KDE3.5 desktop: Trinity Desktop <http://trinitydesktop.org/about.php>.