The Google team answers questions about Blink.
Here are the timecodes for the list of questions from the Chrome Site.
1:12 What will be the relationship between the WebKit and Blink codebases going forward?
2:42 When will Blink ship on the Chrome channels Canary/Beta/Stable?
3:25 How does the plan for transitioning the WebKit integrated in Android to Blink look like?
6:40 Can you elaborate on the idea of “removing obscure parts of the DOM and make backwards incompatible changesthat benefit performance or remove complexity”?
8:35 How will Blink responsibly deprecate prefixed CSS properties?
9:30 What will prevent the same collaborative development difficulties that have hampered Webkit emerging in Blink, as it gains more contributors and is ported to more platforms?
12:35 Will changes to Blink be contributed back to the WebKit project?
13:34 Google said problems living with the WebKit2 multi-process model was a prime reason to create Blink, but Apple engineers say they asked to integrate Chromium’s multi-process into WebKit prior to creating WebKit2, and were refused. What gives?
16:46 Is the plan to shift Android’s
17:26 Will blink be able to support multiple scripting languages? E.g. Dart.
19:34 How will affect other browsers that have adopted WebKit?
20:44 Does this means Google stops contributions to WebKit?
21:31 What Open Source license will Blink have? Will it continue to support the H.264 video codec?
22:11 Any user-agent string changes?
23:38 When we’ll be able to test first versions of Blink in Chromium?
24:15 How can developers follow Blink’s development?
25:40 What is chromestatus.com about?
26:40 How will this impact Dart language’s progress?
27:13 Will this be a direct competitor against Mozilla’s new engine?
29:03 When will all existing vendor prefixes in Blink be phased out?
30:20 Will you support -blink-text-decoration: blink? 😉