That is true too (when we announced b2g aka FirefoxOS, ChromeOS friendlies privately mailed good wishes and lamented “we’re not allowed to do phones”; this was late July 2011).
-
-
This Tweet is unavailable.
-
Replying to @andreasgal @crzwdjk and
The ChromeOS friendlies said they had working phones but weren’t allowed, so yeah: management, path dependent development. Android tried to play safe with Linux + Java, but JS in V8 was getting fast even before Chrome released in fall 2008. Might ChromeOS eat Android over time?
2 replies 0 retweets 11 likes -
Replying to @BrendanEich @andreasgal and
I think this (about management) is also a little unfair. If I were in that position, I'd struggle to reconcile having two OSes. In 2009, deskops and phones were just different OSes. (Same w/ Windows, iOS.) In 2018, not quite. But just dropping either one on the floor seems dumb.
1 reply 0 retweets 1 like -
Replying to @spongeclipper @andreasgal and
No one wanted anything dropped, just faster action killing Gingerbread (whose WebKit version w/ OEM-added bugs made it the IE of the mobile web), for a start. Water way under the bridge by now.
1 reply 0 retweets 2 likes -
Replying to @BrendanEich @andreasgal and
I was responding to the point about internal power struggles. Would having chromeos *also* on mobile (complete with its own app ecosystem) have been better? It’s easy to see “attempts to cohere” as “power struggles,” but ultimately goog was a victim of having two successful OSes.
1 reply 0 retweets 2 likes -
Replying to @spongeclipper @andreasgal and
Such victim! :-P No, in late July, 2011 (the date in question), ChromeOS was not yet a success. See https://en.m.wikipedia.org/wiki/Chrome_OS . The issue then, for ChromeOS, B2G at Mozilla, many, was whether the bigs would invest in Web to match native. 2 security models vs 1. Chrome in ICS, etc.
1 reply 0 retweets 1 like -
Replying to @BrendanEich @spongeclipper and
What we got was a drawn out muddle that smelled of infighting of nonvictim super-rich. This included not just Android but GooglePlus. It was a larger-scale variant on Dart & PNACL follies. Nice work/pay for a few, net-negative effects on Web for many. Better now but at high cost!
1 reply 1 retweet 5 likes -
Replying to @BrendanEich @spongeclipper and
At any stage, 2005 (I knew Andy from Danger, which used Gecko in cloud) to ‘08 to ‘11, bets had to be laid. No blame for picking Linux+Java in ‘05. But “rich companies can make multiple OSes” does not require that they do (cf. MSFT). B2G & ChromeOS comrades saw better bet in ‘11.
1 reply 2 retweets 6 likes -
Replying to @BrendanEich @andreasgal and
I've honestly lost track of what were arguing. Clearly the iOS/Android security argument is not about Java vs web. Maybe about differing business models, but isn't that about how devices (phones, laptops) are made and bought?
2 replies 0 retweets 0 likes
We're all in line at Arby's
-
-
Replying to @Pinboard @BrendanEich and
So, you getting roast beef, or labor organizing of a traditionally anti-union white-collar industry?
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.