4 ms·

So the main ingredient in the browser: rendering engine does not matter enough and you can claim making your browser yourself if you did everything around it? C

So the main ingredient in the browser: rendering engine does not matter enough and you can claim making your browser yourself if you did everything around it? Cool, I can code my own browser from scratch in about an hour, just drop in WebView and add some controls.

pyre 16y ago
From the comments that some people are making here you would have to think that the content of the Chrome binary was: #!/bin/sh exec webkit Which is not the truth. If you're going to rail against Google's claims, then go ahead, but don't start making up crap and/or under-estimating the amount of work that they did just because you think that it makes your argument look more appealing.
- rimantas 16y ago
  Don't you think you underestimate the amount of work that went into Webkit development? Or are you claiming that it is really minor compared to everything else in Chrome? Because only then claim "we made everything from scratch" makes sense. I really fail to see how pointing that one of the main components was not developed by Google from scratch counts as "making up crap".
  - pyre 16y ago
    > Don't you think you underestimate the amount of work that went into > Webkit development? Or are you claiming that it is really minor > compared to everything else in Chrome? Because only then claim "we > made everything from scratch" makes sense. > > I really fail to see how pointing that one of the main components > was not developed by Google from scratch counts as "making up crap". You fail to understand my comment. I was commenting on people claiming that the non-WebKit parts of Chrome are (effectively) boilerplate. The difference between claiming that Chrome is 95% WebKit, 5% Google code and a reality of (probably something like) 70% WebKit, 30% Google code is meaningful. Maybe not meaningful when talking about 'everything from scratch,' but let's not lower ourselves by resorting to overstatements just because it makes us feel better when we are ranting against something, no?

pyre 16y ago

From the comments that some people are making here you would have to think that the content of the Chrome binary was: #!/bin/sh exec webkit Which is not the truth. If you're going to rail against Google's claims, then go ahead, but don't start making up crap and/or under-estimating the amount of work that they did just because you think that it makes your argument look more appealing.

rimantas 16y ago
Don't you think you underestimate the amount of work that went into Webkit development? Or are you claiming that it is really minor compared to everything else in Chrome? Because only then claim "we made everything from scratch" makes sense. I really fail to see how pointing that one of the main components was not developed by Google from scratch counts as "making up crap".
- pyre 16y ago
  > Don't you think you underestimate the amount of work that went into > Webkit development? Or are you claiming that it is really minor > compared to everything else in Chrome? Because only then claim "we > made everything from scratch" makes sense. > > I really fail to see how pointing that one of the main components > was not developed by Google from scratch counts as "making up crap". You fail to understand my comment. I was commenting on people claiming that the non-WebKit parts of Chrome are (effectively) boilerplate. The difference between claiming that Chrome is 95% WebKit, 5% Google code and a reality of (probably something like) 70% WebKit, 30% Google code is meaningful. Maybe not meaningful when talking about 'everything from scratch,' but let's not lower ourselves by resorting to overstatements just because it makes us feel better when we are ranting against something, no?