By nanofish
via arstechnica.com
Published: Sep 09 2008 / 15:59
In the wake of Google's release of the new WebKit-based Chrome browser, some technology enthusiasts are beginning to wonder if the days are numbered for Mozilla's Gecko rendering engine. Despite the growing popularity of WebKit, those who understand the differences between the two rendering engines and have an appreciation of Gecko's technical strengths, recognize that there is no basis for speculation about the possibility of Mozilla adopting it for future versions of Firefox.
-
45+ Excellent Website Analytics/Monitoring/Counter Services
-
A Simple Add, Edit, Delete, and Search using VB and MSAccess
-
IT Salaries and Contract Rates Holding Despite Job Losses
-
Open an issue when a test fails during a TFS build
-
Acquia Search becomes publicly available
-
Tutorial: jQuery Fold Effect Concept And Explanation
Comments
figital replied ago:
I'm sure Apple also chose the KHTML engine because it had a BSD-style license ... so they can do whatever they want with code (OSX is also FreeBSD). That wasn't going to happen with Mozilla.
killerweb replied ago:
See I actually thought people knew this thinking already. It's not, and has never been about the rendering engine of HTML/JS. Adoption of browsers has always been about "word of mouth", "what's cool" & extensions. This is why IMHO, Google only hurt the community, not helped it. They should have PUSHED Firefox to higher standards instead of fragmenting an already fragmented user base. The Firefox team has worked their asses off to get as far as they did. Adopting rendering engines to help ease the pain of dual efforts has been in the works for a while. My hope is one day being able to code some rich app that doesn't need rework because some "standard-less browser" decides to do, "what it thinks is better"...IE6..Cough..Cough..Cough
Voters For This Link (16)
Voters Against This Link (0)