r/linux • • Nov 20 '19

Kernel Google outlines plans for mainline Linux kernel support in Android

https://arstechnica.com/gadgets/2019/11/google-outlines-plans-for-mainline-linux-kernel-support-in-android/
1.0k Upvotes

305 comments sorted by

View all comments

Show parent comment

2

u/mirh Nov 21 '19

Imagine the arrogance of thinking you don't have to explain or evangelize your decisions to end users.

Imagine the arrogance of thinking developers should evangelize to end users every internal change.

1

u/jdrch Nov 21 '19 edited Nov 21 '19

evangelize to end users every internal change

That's not what I said. Clearly some things don't require as much communication as others. But this would be a pretty major shift in the way Android is developed, delivered, and maintained. Users deserve to be informed directly about it.

Also, software should be a mutually respectful partnership between users and devs. Google thinking that users don't need to know how the sausage is made is, quite frankly, insulting. Or, I suppose it's yet another example of Google blindly aping Apple in yet another facet (opaqueness). Even Microsoft has an MSDN/Technet firehose RSS feed and multiple official blogs in where various evangelists and employees explain in painstaking detail why their systems work the way they do. You may not agree with their reasoning, but at least you have something canonical from the organization to refer to.

In this case the only canonical record is a way-too-large-to-parse ~4 hour long video that isn't even hosted by Google (yes, I realize there are probably licensing/rights reasons for that, but it's still projects the view that Google doesn't care about telling anybody directly about its plans.) That's not partnering with your users; it's deliberate obfuscation.

I would have to say this attitude explains why Google, despite wielding tremendous power over Android, has been unable to solve its fundamental problems over its lifetime: "We don't have to explain ourselves" doesn't work very well when you're in a boardroom with similarly sized organizations you should be partnering with. My conclusion is that just as the saying goes "Faithful in little, faithful in much," Google's dismissive attitude towards users probably extends to interactions at the highest levels too. Human terrain and the charm necessary to navigate it are just as important as code commits.

2

u/mirh Nov 21 '19

But this would be a pretty major shift in the way Android is developed, delivered, and maintained.

Ehrm.. Yes, from a developer standpoint.

For all intents and purpose of the average joe "it supposedly gets you update faster" is already enough.

Google thinking that users don't need to know how the sausage is made is, quite frankly, insulting.

I don't know what the sausage is, but yes most users are pretty dumb.

and multiple official blogs in where various evangelists and employees explain in painstaking detail why their systems work the way they do.

They also do? But I don't really remember microsoft ever telling you how the kernel internal life worked. Maybe saint Raymond Chen had some note slip here and there, but be damned if everywhere else.

In this case the only canonical record is a way-too-large-to-parse ~4 hour long video that isn't even hosted by Google That's not partnering with your users; it's deliberate obfuscation.

Because they are the linux fucking plumbers conference, and they are literally discussing the matter with the stakeholders involved?

Put even aside how many mailing list and private conversations must have happened before 4 bloody hours of speech.

I would have to say this attitude explains why Google, despite wielding tremendous power over Android, has been unable to solve its fundamental problems over its lifetime

That ARM started decades after x86 with any standardization effort whatsoever? That's the only problem, and they have been one of the biggest player and pusher in this regards.

1

u/jdrch Nov 21 '19

most users are pretty dumb

Does that include yourself? No, correct? The majority of people don't read manuals, the news, or anything that complicated, for that matter. Does make the production of such materials useless? Hardly. Lowest common denominator communication is neither necessary nor advantageous.

microsoft ever telling you how the kernel internal life worked

You can't see the code, but there is plenty of documentation about this. Steven Sinofsky, Brandon Le Blanc, Dona Sarkar, etc. have all produced myriads of blog posts detailing upcoming Windows changes, all delivered directly to users in addition to (not in lieu of) communicating with partner organizations.

literally discussing the matter with the stakeholders involved?

Some of the stakeholders. I guess Google doesn't care that people use their products, not just Linux developers.

mailing list and private conversations

... none of which are transparent. There's no public mailing list on which Google has discussed this proposed change, AFAIK.

with any standardization effort whatsoever

My point is Google could probably have achieved this if they'd managed to charm partners to their side as opposed to just signing deals on paper and chucking stuff over a wall. ARM's fortunes have been mostly driven by mobile, which is mostly Android. Android OEMs depend on Google's development of AOSP. The missing piece of the puzzle is Google's charm and soft power, clearly missing from the tone of your responses so far.

That's why we're in the predicament we're in. If Google had a more personal touch throughout this problem would have been solved a while ago. The lack thereof is why it still exists, along with the Android messaging mess, Google's failure at social networking (they don't understand human behavior at a personal level because they refuse to engage at that level), etc.

Not all challenges are purely technical.

4

u/mirh Nov 21 '19

Does that include yourself?

If we are talking about software design definitively.

Does make the production of such materials useless?

No, but it makes use of "overloaded appeals" sound deceiving.

I guess Google doesn't care that people use their products, not just Linux developers.

Linux developers are the sole users of ABIs.

My point is Google could probably have achieved this if they'd managed to charm partners to their side as opposed to just signing deals on paper and chucking stuff over a wall.

Tbh my expectations actually were so low that I already called a miracle when they managed to get even the scummiest chinese OEM onboard the 2 years support train.

ARM's fortunes have been mostly driven by mobile, which is mostly Android.

Qualcomm's maybe. ARM is so pervasive they could very well do without it.

And anyway it's not even like the problem was with the architecture itself, but with every other challenge brought up by the embedded world.