4 ms·

I disagree, many of us wanted this but none of us had the money to fund it... Google has a special kind of magic for the time... IBM would fund some developers

by taf2 4y ago

I disagree, many of us wanted this but none of us had the money to fund it... Google has a special kind of magic for the time... IBM would fund some developers to work on Mozilla... Mozilla had some money to fund development on Mozilla... Apple had a few funds for developers to maintain a browser for Apple... Microsoft was happy to maintain IE... Google was different it was a place for innovation. It disrupted search, email (gmail) and mapping (google maps)... now to support those 3 products it made sense to fund a better browser... then with the purchase of YouTube... 4 disruptive web based platforms it made even more sense to fund a browser. I hear chrome team saved youtube billions in network costs (per year) just by ensuring more adoption of vp8/9... Today we tend to focus more on the ad business Google purchased doubleclick and the evils of it's tracking... but think back to this Google had at least 5 major disruptive technologies... search, email, mapping, video consumption, and the 5th IMO... enabling countless businesses to build successful web applications because of the development of a "good" browser.

cmrdporcupine 4y ago
You're not getting the point. Chrome never needed to slay itself, because there was no customer expecting delivery. It literally couldn't be late because there was no set schedule. It was done when the engineers finished it. Like many projects at Google. My experience in general is they don't do schedule-discipline well at all. And management there seems to think throwing ever more headcount at things will make them ship faster (it rarely does). And there's very little accounting when promised dates are missed. Even by years. I worked on the software for Home Hub, and everything was supposed to get rewritten in Fuchsia, and they promised to be ready in like two quarters, almost immediately after we shipped it. They had unlimited headcount and the blessing of upper management, but failed schedule after schedule with no consequence. It took them another two and a half years.
SahAssar 4y ago
Wanted or not, nobody (or at least not many people) asked for google to make a browser, and nobody waited for it, which was what the parent comment said. Also I had a really hard time reading your comment with all the ellipses making it seem like it was just a huge sentence, that might just be me though.
alisonkisk 4y ago

by taf2 4y ago

cmrdporcupine 4y ago

You're not getting the point. Chrome never needed to slay itself, because there was no customer expecting delivery. It literally couldn't be late because there was no set schedule. It was done when the engineers finished it. Like many projects at Google. My experience in general is they don't do schedule-discipline well at all. And management there seems to think throwing ever more headcount at things will make them ship faster (it rarely does). And there's very little accounting when promised dates are missed. Even by years. I worked on the software for Home Hub, and everything was supposed to get rewritten in Fuchsia, and they promised to be ready in like two quarters, almost immediately after we shipped it. They had unlimited headcount and the blessing of upper management, but failed schedule after schedule with no consequence. It took them another two and a half years.

SahAssar 4y ago

Wanted or not, nobody (or at least not many people) asked for google to make a browser, and nobody waited for it, which was what the parent comment said. Also I had a really hard time reading your comment with all the ellipses making it seem like it was just a huge sentence, that might just be me though.

alisonkisk 4y ago