This is all what I can recall so don't consider it 100% accurate but I'm pretty much sure about the main point, which is that it simply was not viable to develop khtml from a practical standpoint. At the time KHTML was the first to pass ACID2 test and beat competition performance-wise in many aspects. It's still fascinating what they achieved though. It was not really feasible for KHTML to compete with so many new specs being introduced to the web. That was the beginning of browser wars when Apple and Google were both funding Safari and Chrome with millions of dollars. You see, Konqueror as a web browser didn't even have a single full time developer. There were occasional commits by other people but the majority of KHTML's development was done by him. I was only around in the last year or two but KHTML was mostly developed by a single volunteer on his spare time (Hi SadEagle in case you're reading this). I don't think it was KDE 3 -> 4 transition that killed khtml. straight from the file attach feature in an instant messenger.ĭesktop Linux was a lot less friendly to get working smoothly back then compared to now, and feature discovery was by word of mouth more than anything, but it sure felt like living in the future early. The rip and encoding would happen on the fly, and you could do this e.g. Ripping a music CD into MP3s was similar - you'd open the volume in the file manager and see your tracks along with a virtual folder full of MP3 files. KDE always came with a lot of VFS trickery like that. I remember using this regularly to mass-download the images embedded into a page - open the page this way by replacing with a pseudo-protocol, copy all, paste, done. in Open File dialogs from anywhere within the toolset. It was a plugin to the VFS framework (KIO) the desktop and all the apps use, so it would also work e.g. Think like a client-side generated version of Apache's index pages, but using your local file manager. KDE on Linux used to have something similar in the late 90s - it allowed you to open a website URL as a directory listing, so you could browse the site's asset directories and open image files, etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |