While at the same time opening new positions for Pixel teams in Poland, for example.
this post was submitted on 11 Apr 2025
131 points (97.8% liked)
Technology
70214 readers
27 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
Well, if you don't need programmers to work in place place at the corporate headquarters, you can hire them anywhere.
Why would they need more staff if they plan on developing it in a closed source manner now?
Android has always been developed in a closed-source manner by Google engineers, the recent changes only reduces the visibility of ongoing changes and the ability for developers outside of OEMs to contribute to Android (such contributions were already rare).
This is explained further in this article:
While some OS components, such as Android’s Bluetooth stack, are developed publicly in the AOSP branch, most components, including the core Android OS framework, are developed privately within Google’s internal branch. Google confirmed to Android Authority that it will soon shift all Android OS development to its internal branch, a change intended to streamline its development process.
the recent changes only reduces the visibility of ongoing changes and the ability for developers outside of OEMs to contribute to Android (such contributions were already rare).
Why is this so underplayed as if it's nearly meaningless though, is my question? A huge part of open source code is transparency, and this decision is a big blow to exactly that.
Only posting the code when it's finished increases the risk that it will not be correctly scrutinized in the way its been until now, not to mention the precedent this sets. Death of the OS in AOSP by a thousand shallow cuts is what I see here.
Maybe that's what they will do now. But that's not what the announcement said.
IIRC that announcement came a couple weeks ago.