What are you talking about? He didn't even STATE an argument! YOU made an argument for him, and then said it was disingenuous. You could have instead assumed he was smart and took the plausible argument of "an organization with a billion plus lines of code is in trouble".
-
-
Replying to @cmuratori @Jonathan_Blow and
He was referencing your argument about complex software stacks, and saying it was even worse than 30M lines because there's billions of lines across all software at google.
1 reply 0 retweets 0 likes -
Replying to @ssylvan @Jonathan_Blow and
IT'S THE SAME ARGUMENT. Do you think all 13 million lines of code in the Linux kernel is compiled into every Linux kernel? What are you even talking about?
3 replies 0 retweets 3 likes -
Replying to @cmuratori @Jonathan_Blow and
It's not the same argument. If you add a million lines to windows, it doesn't make android more complex. Even if you were to copy both source trees into the same folder. That's the point.
2 replies 0 retweets 2 likes -
Replying to @ssylvan @Jonathan_Blow and
Anything that is code that is maintained by Google is a cost to Google. It's engineering that is not going into something else. The measure of the complexity of an organizations total codebase _is very similar to_ the complexity of a product codebase with multiple organizations.
1 reply 0 retweets 3 likes -
Replying to @cmuratori @ssylvan and
So to say that somehow the LOC count on Linux (one project, many organizations) and the LOC count at Google (many projects, one organization) are woefully different, couldn't possibly be related, even in a snarky simple tweet, is just nuts man.
1 reply 0 retweets 1 like -
Replying to @cmuratori @Jonathan_Blow and
It really isn't, though. Android's code base might as well be written by a different company from e.g. gmail on iOS, or window chrome. The fact that they're in the same tree and written by different departments in one big company doesn't increase the complexity.
3 replies 0 retweets 2 likes -
Replying to @ssylvan @Jonathan_Blow and
I just don't even. GMail on Android depends on GMail architectural decisions AND Android architectural decisions, right? A bug in either will make a bug in it. A bug in Chrome makes a bug in GMail client. A bug in search makes a bug in Assistant.
2 replies 0 retweets 3 likes -
Replying to @cmuratori @ssylvan and
But more importantly, an engineer working on Assistant is not working on GMail. One working on Android isn't working on DeepMind. IT MATTERS HOW MUCH WORK THERE IS TO. Programming is a finite resource. The more LOC you have, the less expertise you have across it.
1 reply 2 retweets 12 likes -
This Tweet is unavailable.
Twitter needs to make post-only accounts a thing, where you can just permanently prohibit any tweet with your at-name or hash-name in it.
-
-
This Tweet is unavailable.
-
This Tweet is unavailable.
- Show replies
-
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.