Why Mozilla Is Committed To Using Gecko

Ars Technica has published an article about Mozilla's commitment to use the Gecko rendering engine instead of using Webkit, which was adopted by Apple and Google for use in the Safari and Chrome browsers. I have been using Chrome on my work PC and find many of its features compelling, and wonder how soon we will see its best innovations in Firefox. Why is Gecko worth keeping if it is outdated and bloated?

Comments

Re:lite

[bigstrat2003]

I'm aware that people have been asking for it for a long time. I recall reading people calling for this feature on /. at least a year ago. If it were a new idea, I would cut Firefox some slack, but it isn't, so they get none.

And by "threaded tabs", I mean using threads or separate processes. I know that it'll probably be easier for developers to achieve the stability I seek with processes, but I also am not willing to state that it can't be done with threads, so I'll accept either as long as it gets the job done.

Re:Woah...

[slashtivus]

Interestingly enough in C#: int i = 0; i = i++ + i++; results in i = 1. I would have expected 3 or possibly 2. Apparently it ignores the second part? Any insight?