Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

From what I understand, the Chromium web browser will ditch a lot of Google's code, but I don't understand what features will be purged. The announcement is too technical for me; is there a list of features to be removed from an end-user perspective?

Note: My main concerns are the ability to sync with Google accounts and installing extensions from the Chrome Web Store.

share|improve this question
1  
Actually, it is the opposite way around. Chrome and chromium will stop using webkit, so the webkit engine can dump all the chrome/chromium specific code. Chrome/chromium will use the new Blink engine by Google, and should not have any functional difference to now. –  Paul Apr 10 '13 at 1:04
    
@Paul I don't know why you commented, you should have posted it as an answer. Thanks! –  f.ardelian Apr 10 '13 at 1:21

2 Answers 2

up vote 3 down vote accepted

Chromium isn't ditching Google's code. Both Chromium and Chrome are ditching WebKit, which is its current rendering engine (and which is not even remotely a Google product), for a custom fork called Blink. The announcement you saw was from a Webkit developer working for Apple, who has nothing whatsoever to do with Google or Chromium.

share|improve this answer
    
The news website I found it on said it was about Chromium... Thanks for the clarification! –  f.ardelian Apr 10 '13 at 1:19
    
Google is not ditching WebKit per say. They are indeed forking the project but only because of all the stuff being added to Webkit that Google didn't need. They are still going to backport the rendering portion of Webkit into Blink ( likely submit their own changes to Webkit ). –  Ramhound Apr 10 '13 at 11:32

Google has announced that it's going to fork WebKit into Blink, a new rendering engine for Chrome. This is their claim from the announcement:

In the short term, Blink will bring little change for web developers. The bulk of the initial work will focus on internal architectural improvements and a simplification of the codebase. For example, we anticipate that we’ll be able to remove 7 build systems and delete more than 7,000 files—comprising more than 4.5 million lines—right off the bat. Over the long term a healthier codebase leads to more stability and fewer bugs.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.