Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Blink: A rendering engine for the Chromium project

blog.chromium.org

Post reply on HN
Print view View original

41–50 of 326 posts

Re: Blink: A rendering engine for the Chromium project

#42

Post by cpeterso »

The good news is no -blink prefixes! Blink, like Mozilla, will avoid shipping vendor-prefixed features:

  Historically, browsers have relied on vendor prefixes (e.g., -webkit-feature) to 
  ship experimental features to web developers. This approach can be harmful to 
  compatibility because web content comes to rely upon these vendor-prefixed 
  names. Going forward ... we will instead keep the (unprefixed) feature behind
  the “enable experimental web platform features” flag in about:flags until the 
  feature is ready to be enabled by default.

Re: Blink: A rendering engine for the Chromium project

#44

Post by nickporter »

Joeri wrote: post #31

Google seems on a "replace open with less open" streak, with google reader and caldav shuttering, and now this. The caldav situation especially i cannot conceive as anything but a business decision given that they're keeping it around for those people they like.

This has absolutely nothing to do w/ Google Reader.

Also: https://code.google.com/p/chromium/

Re: Blink: A rendering engine for the Chromium project

#45

Post by beshrkayali »

mtgx wrote: post #33
gsnedders wrote: post #17

Earlier quoted context omitted.

No, it just means that instead of Chrome for Android and Chrome for iOS having different versions of WebKit, Chrome for Android will use Blink and Chrome for iOS will use the system WebKit, as it does now.

So Google will be using 2 increasingly different rendering engines for Chrome in the future? Well that sucks. Apple really needs to allow other rendering engines on iOS, or at least be forced into it. People complain about the "webkit mono-culture", but a huge platform like iOS actually mandating you use webkit, and their single version of webkit, is a lot worse.

I agree, that would suck. Specially if -for some reason- we start seeing differences in terms of rendering speed/js engine/or other techs between the android version and the iOS version.

Re: Blink: A rendering engine for the Chromium project

#46

Post by mikewest »

nickporter wrote: post #40

Super excited about this! There was a long discussion on the webkit mailing list after google tried to add support for multiple language VMs in webkit. The goal was to have a native Dart VM. https://lists.webkit.org/pipermail/webkit-dev/2011-December/... If I remember correctly, the patch was not merged in. I guess now google can do whatever it wants!

"Whatever it wants" within reason. We're actually quite concerned about how new features are added to the web platform, and recognize the need to be careful about what we commit to support forever. See http://www.chromium.org/blink#new-features for some detail about the process we're planning on using going forward.

Re: Blink: A rendering engine for the Chromium project

#49

Post by mikewest »

cpeterso wrote: post #42

The good news is no -blink prefixes! Blink, like Mozilla, will avoid shipping vendor-prefixed features: Historically, browsers have relied on vendor prefixes (e.g., -webkit-feature) to ship experimental features to web developers. This approach can be harmful to compatibility because web content comes to rely upon these vendor-prefixed names. Going forward ... we will instead keep the (unprefixed) feature behind the…

Yes! Prefixes are damaging. We're hiding things behind flags instead, which gives savvy developers the chance to experiment without the risk that sites will begin to depend on those experiments.
Post reply on HN