JIT

From Gnash Project Wiki

Jump to: navigation, search

JIT-compiling (or why using bytecode is doublethink (or why Markus like gcj))

After reading thru the public info on Adobe's flashplayer (http://labs.adobe.com iirc, my benzo-brain-memory has got corruptions) they are currently using a JIT-compiler and a garbage-collector. My words on JIT-compilation are unprintable. The schism between me (and about anyone worth mentioning studying Computer Science at Linköping's University) and Prof. A. Haraldsson (I invite you to get your world rumbled by it's fundaments) made me realize that this actually *had* it's use back in the days of the 1970ies. Having this said; for me bytecompiling is trying to correct a bad design. SUN did it as well, (the GCC team created gcj and made Java a decent quick-n-dirty-dev-language) since as most of you guys know, it was dead slow back in '96 before the JIT-compiler. GCJ made it work even more flawless.

IMNSHO JIT-compilation is not a good approach at all. It's flawed by design, since pretty much you want to avoid parsing the code so you invent a layer on top of that, just compile the bytecode again.

Albeit the approach used to day in gnash (pretty much interpretative) might be considered for re-design in the future.

An outline on a manifesto for the free (digial) world:

Eric S. Raymond once wrote: "Shut Up And Show Them The Code". But this is not getting us anywhere as long companies are able to force restrictions upon us, the end-users. Having this in mind I'd paraphrase him and write: "Shut up and GPL the code".

After all we'll beat down the closed-source community with this bat, after all we own the hardware and therefore we must be able to know what's running on top of it; After all the information will become free as in freedom.

I'm an intellectual (or that's just something people are lying to me about ;)) and I'm sophisticated, but the most important thing is that 'I am free' in the sense of intellectual freedom.

--Nihilus 21:31, 7 February 2008 (EST)