KDE browser work team
Aaron J. Seigo
aseigo at kde.org
Wed Jul 1 22:10:41 BST 2009
On Wednesday 01 July 2009, Stefan Majewsky wrote:
> what developers need. Perhaps the developers are already quite efficient,
> but just too less. RFC?
it's a three headed monster that we face:
* the web continues to grow in features and complexity at a great pace (this
means more work for web stack developers to keep up with it all)
* web developers only test against web stacks that have "enough usage", which
means in practice IE, Gecko and WebKit. so workarounds, where needed, often
appear in the websites themselves for those engines. that means those stacks
actually have _less_ work to do since the work-arounds are often supplied for
them by website developers.
* KHTML has a dedicated, efficient and hard working team, but it's numbers are
so the situation is a real limit on developer resources on a stack that gets
very little testing against by web developers with very rapidly evolving web
barring dozens of more KHTML developers and significant market sure (more than
KDE's total market share, actually :) this situation will not improve.
note that KHTML remains a great option for non-web-browser in-application use
for many (though not all) applications. in-application use of QtWebKit or
KHTML is actually a very different kind of discussion with very different
issues (e.g. API relevance) ...
regardless, at this point we need people writing code, not so much writing
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
KDE core developer sponsored by Qt Software
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 197 bytes
Desc: This is a digitally signed message part.
More information about the kde-core-devel