Slashdot Mirror

← Back to Stories (view on slashdot.org)

Why Mozilla Is Committed To Using Gecko

Posted by Soulskill on from the gecko,-not-geico dept.

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?

4 of 632 comments (clear)

  1. Why use Gecko? by suck_burners_rice · · Score: 5, Funny

    Because it has a cooler name than the boring sounding WebKit. Besides, it'll save you 15% on car insurance.

    --
    McCain/Palin '08. Now THAT's hope and change!
  2. Re:Woah... by Anonymous Coward · · Score: 5, Funny

    You've begged the question, there

    GOD DAMNIT! No, Begging the question is a logi... wait, you used it RIGHT?

    *reads it again*

    Okay... WHO ARE YOU AND WHAT HAVE YOU DONE WITH SLASHDOT!?

  3. Re:lite by Anonymous Coward · · Score: 5, Funny

    slashdot would suck without multiple threads.

  4. Re:lite by sir+fer · · Score: 5, Funny

    3. Threads introduce WHOLE NEW CLASSES of bugs

    ah, so that's why MS is so keen on adopting multi-threaded programs.

    1.Introduce new buggy software

    2.Offer paid support for said software

    3.Eventually fix old bugs but introduce new ones

    4.Profit

    --
    Debian FTW ;o)