| GeneralAntilles |
2009-06-24 23:50 |
Re: goodness, nit is slow
Quote:
Originally Posted by danramos
(Post 299445)
Why DOES Nokia prefer to include such a terribly slow implementation on a product that was primarily intended to be an Internet device?
|
Gecko was the best thing available when they started work on MicroB, unfortunately its development soon sped ahead of Nokia after that. As for why they didn't ship a real update (which would improve the JS times by leaps and bounds), well, they had diverged a lot from trunk, were in the "fixes only" period and couldn't really manage going that unstable for Diablo.
Too bad, really, but what can you do? Thankfully upgrading the engine in the fully-opensource Fremantle MicroB should be a lot simpler.
Quote:
Originally Posted by danramos
(Post 299454)
Agreed, they worked with what they had at the time--but no, wait.. WebKit's been around for a LONG time now, hasn't it? hmmmm. :) And didn't they start out with Opera and switch to the gecko engine? Why didn't they do continue that trend on to webkit?
|
WebKit was a joke at the time they started work on MicroB. While it's certainly seen huge improvement since then, you're delusional if you think it's so much better than Gecko now that it would justify the time and costs that it would take to do another engine migration.
Besides, Nokia has plans for XULRunner and WebKit doesn't offer anything equivalent.
Whatever, I've been over all of this several times before. Trust me (or don't) when I say they have good reasons for doing things as they have.
|