WebKit for Keynote

An inter­est­ing email passed through the webkit-​dev mail­ing list today. In what appears to be a small glimpse into what goes on in prepa­ra­tion for a Stevenote, Geof­frey Garen (Apple) noted in a reply to an email from Akos Kiss (Depart­ment of Soft­ware Engi­neer­ing, Uni­ver­sity of Szeged, Hun­gary) that one of the rea­sons WebKit likes to do its own thing and not depend on code it doesn’t own is to be able to fix prob­lems with very short notice. Citing the exam­ple of, “12 hours before a keynote address”.

Akos Kiss (Depart­ment of Soft­ware Engi­neer­ing, Uni­ver­sity of Szeged, Hungary):

b) JIT com­pi­la­tion to Java byte­code or Action­Script bytecode.

Com­ment: Huge work. Cur­rently avail­able com­piler imple­men­ta­tions do not fit to the archi­tec­ture of the JS engine.

Geof­frey Garen (Apple):

Right. We’re also reluc­tant to rely on code that we don’t own. We’ve seen very large per­for­mance wins from tightly inte­grat­ing and cus­tomiz­ing all the com­po­nents of the web stack. We also need the free­dom to fix crashes and com­pat­i­bil­ity prob­lems on very short notice (for exam­ple, 12 hours before a keynote address).

Leave a Reply