Link Details

Link 911801 thumbnail
User 225256 avatar

By mswatcher
Published: Jan 25 2013 / 10:04

Counter to the opinion of the Web Development literati, I support a WebKit monoculture. I’ll put this in no uncertain terms: I think the web would be better off if WebKit was the only rendering engine. The common arguments against this are that it’s bad for competition and that “it’s IE6 all over again”. I feel that the former argument is invalid, and the latter is a false dichotomy.
  • 8
  • 2
  • 800
  • 605
User 161039 avatar

mheath replied ago:

0 votes Vote down Vote up Reply

This would be great. Then we could get rid of the HTML specification altogether. After all, what's the point of having a spec if there's only one implementation. The spec is the code baby!

User 1105459 avatar

sonnycleon replied ago:

-2 votes Vote down Vote up Reply

I would love to see the pictures and the movie, after passing through many sites i have found a very impressive website and or that is .regularly update the movie and very good support

User 226303 avatar

devdanke replied ago:

0 votes Vote down Vote up Reply

I'm satisfied that the majority of mobile apps run on WebKit. Currently, Google and Apple invest heavily in WebKit and it shows. It's a fast, stable rendering engine, with rapidly advancing multi-media abilities (sound & audio). Having Firefox around is also good. It's keeps WebKit from being a monopoly (which could be unhealthy). But the best thing about WebKit dominance is that it makes IE a non-factor in mobile development. For long painful years web development suffered from Microsoft's crappy, backward, buggy, insecure browser. Thank goodness we don't have to deal with that now. WebKit's dominance keeps IE out of play (at least in the mobile space)!

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Apache Hadoop
Written by: Piotr Krewski
Featured Refcardz: Top Refcardz:
  1. Play
  2. Akka
  3. Design Patterns
  4. OO JS
  5. Cont. Delivery
  1. Play
  2. Java Performance
  3. Akka
  4. REST
  5. Java