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

Google Forks WebKit And Launches Blink, A New Rendering Engine

techcrunch.com

Post reply on HN
Print view View original

1–10 of 40 posts

Re: Google Forks WebKit And Launches Blink, A New Rendering Engine

#3

Post by ChuckMcM »

" the decision to fork WebKit was entirely driven by the engineering teams and solely based on the fact that the engineers felt constrained by the technical complexity of working within the WebKit ecosystem."

Is this code for "They wouldn't take our changes so we said, 'Fork it!' and made our own." ?

Re: Google Forks WebKit And Launches Blink, A New Rendering Engine

#5

Post by mooism2 »

ChuckMcM wrote: post #3

" the decision to fork WebKit was entirely driven by the engineering teams and solely based on the fact that the engineers felt constrained by the technical complexity of working within the WebKit ecosystem." Is this code for "They wouldn't take our changes so we said, 'Fork it!' and made our own." ?

“Currently, the majority of WebKit reviewers are from Google (95), with Apple coming in second (59)... Google is also currently responsible for the vast majority of commits to the WebKit repository...”

Doubtful.

Re: Google Forks WebKit And Launches Blink, A New Rendering Engine

#6

Post by dragonwriter »

ChuckMcM wrote: post #3

" the decision to fork WebKit was entirely driven by the engineering teams and solely based on the fact that the engineers felt constrained by the technical complexity of working within the WebKit ecosystem." Is this code for "They wouldn't take our changes so we said, 'Fork it!' and made our own." ?

> Is this code for "They wouldn't take our changes so we said, 'Fork it!' and made our own." ?

I think its probably more exactly what it says -- a way of eliminating the overhead of dealing with the complexity of the WebKit ecosystem. As noted in the article, "Google says, for example, that it will 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."

That's a whole lot of complexity that isn't relevant to what Google is doing with Chrome that is worth not having to deal with.

Re: Google Forks WebKit And Launches Blink, A New Rendering Engine

#7

Post by crimsonzagar »

This is just a personal opinion, but for a browser I'd always support and use a not-for-profit one. No matter how fast, or perceptibly fast, an offering from a business entity is.

Here is why: 1. Tomorrow you, the billion dollar enterprise, will force real identity even more vehemently. 2. I certainly don't want to see a constant hum of ads. 3. I don't want to turn my computer into a wide-mouth bucket for chrome apps, for example, which have higher than normal access and rights on my disk.

Your browser could potentially take me back into an era of 'download-yet-another-snoopy-app' into your machine yeah! Put it all behind a curated garden and keep me happy within. Where web on tablets and smartphones is today. Nope, not for me.

Re: Google Forks WebKit And Launches Blink, A New Rendering Engine

#8

Post by drivebyacct2 »

ChuckMcM wrote: post #3

" the decision to fork WebKit was entirely driven by the engineering teams and solely based on the fact that the engineers felt constrained by the technical complexity of working within the WebKit ecosystem." Is this code for "They wouldn't take our changes so we said, 'Fork it!' and made our own." ?

Pretty sure it has more to do with their architecture changes RE: multithreading and embedding/porting.

Re: Google Forks WebKit And Launches Blink, A New Rendering Engine

#9

Post by jmillikin »

crimsonzagar wrote: post #7

This is just a personal opinion, but for a browser I'd always support and use a not-for-profit one. No matter how fast, or perceptibly fast, an offering from a business entity is. Here is why: 1. Tomorrow you, the billion dollar enterprise, will force real identity even more vehemently. 2. I certainly don't want to see a constant hum of ads. 3. I don't want to turn my computer into a wide-mouth bucket for chrome apps…

Current popular browsers are:

  * Firefox
  * Chrome / Chromium
  * Internet Explorer
  * Safari
  * Opera
All of them are produced with the aim of benefiting their parent corporations in some way -- for example, Mozilla Corp rents the default search engine setting to Google for hundreds of millions per year.

I currently use Firefox and Chromium as my primary browsers, because they are the only popular browsers that are open-source and therefore the only browsers I fully trust. Despite coming from "business entities", neither browser shows me ads, requires me to enter a government-approved name, or requires me to install third-party applications.

Re: Google Forks WebKit And Launches Blink, A New Rendering Engine

#10

Post by mirsadm »

mooism2 wrote: post #5
ChuckMcM wrote: post #3

" the decision to fork WebKit was entirely driven by the engineering teams and solely based on the fact that the engineers felt constrained by the technical complexity of working within the WebKit ecosystem." Is this code for "They wouldn't take our changes so we said, 'Fork it!' and made our own." ?

“Currently, the majority of WebKit reviewers are from Google (95), with Apple coming in second (59)... Google is also currently responsible for the vast majority of commits to the WebKit repository...” Doubtful.

Do you have any proof that the statement is false?
Post reply on HN