That's a good point about KHTML. A long time ago, Konqueror was actually usable as a web browser on most sites. And of course, WebKit has diverged so far...
Maybe what we need is to split up the browser: develop the rendering engine, JS engine, UI, etc, separately, with well-defined APIs. Then the things that require dedicated expertise could be developed by full-time employees, and the results of their work could be integrated into different end-user products, different browsers with different target audiences, developed by different groups, with much less effort and expertise required.
Of course, this is what Gecko and XULRunner used to be. Now Mozilla's direction is just demonstrating how badly needed their former course of action still is.
libgecko, anyone? (or even libservo--but will they handle it the same way they've handled Gecko, and make it practically Firefox-only?)
Maybe what we need is to split up the browser: develop the rendering engine, JS engine, UI, etc, separately, with well-defined APIs. Then the things that require dedicated expertise could be developed by full-time employees, and the results of their work could be integrated into different end-user products, different browsers with different target audiences, developed by different groups, with much less effort and expertise required.
Of course, this is what Gecko and XULRunner used to be. Now Mozilla's direction is just demonstrating how badly needed their former course of action still is.
libgecko, anyone? (or even libservo--but will they handle it the same way they've handled Gecko, and make it practically Firefox-only?)