Google cuts hundreds of jobs in Android division - Hypertext
htxt.co.za
A fresh round of layoffs has hit Google in its device and platforms division, with Microsoft also considering job cuts soon.
  • Google is set to cut hundreds of new jobs in its device and platforms divisions soon.
  • The company has continued to cut its Google Pixel teams, doing so earlier this year as well.
  • Rival Microsoft is considering a new round of layoffs next month, per reports.
  • BlackEco@lemmy.blackeco.comEnglish
    45·
    2 days ago

    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.

    • Pirata@lemm.eeEnglish
      18·
      2 days ago

      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.

      • steal_your_face@lemmy.mlEnglish
        3·
        23 hours ago

        No one really scrutinized it while it was in development anyways. For example graphene os always looked at and made changes to the aosp releases.