Linked by Thom Holwerda on Mon 27th Feb 2012 12:22 UTC
Permalink for comment 508720
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/20/13 6:17 UTC, submitted by MOS6510
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
More News »
Sponsored Links



Member since:
2005-07-12
Because the fat, bloated, slow gecko rendering engine that can't even manage worthwhile hardware video acceleration and if you DARE to use any of the CSS3 blending effects results in scrolling more painful than windows 3.1 on a 386 is going to be SO desirable on a mobile device.
RIGHT.
Maybe instead of wasting time branching into platforms their codebase is completely unsuited to, they could spend some time fixing the various implementation bugs that are over a decade old? You know, like gaps in CSS2 that are teenagers? (like say... bugzilla 915?)
I'm getting a real laugh out of this nonsense of using browser engines and javascript as slower more bloated versions of ROM Basic from 30 years ago... because what low voltage low clock speed devices need is more layers of abstraction giving that 1ghz ARM the performance of 386/40 if you just got off your ass and used a *SHOCK* compiler.
Edited 2012-02-27 19:13 UTC