1229
Google's shocking developer decree struggles to justify the urgent threat to F-Droid (www.neowin.net)
submitted 11 months ago by to c/technology@lemmy.world
298 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 11 months ago (3 children)

Yes, it does apply to every operating system - hence, the differentiator becomes whether the operating system has hundreds of millions of dollars to spend on dedicated security development. This is why a lot of companies now don't even let you use Android devices for BYOD aside from Google or Samsung, because they're the only companies with the resources to keep their security really up to date.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 11 months ago (2 children)

    my point is that if the open source community cannot figure out just maintenance of an android system, there's no chance of creating a real mobile linux distribution, as it would need the aforementioned maintenance and the development of additional features

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 11 months ago* (1 child)

    Ahhh I see, I was confused about what you were getting at. My mistake. And yes that's very true...hmm. More dire than I was even thinking then..

    Honestly this is exactly the kind of thing that taxes and governments are supposed to be good for handling. Failures within failures I suppose!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 11 months ago

    no worries. but that's why I think android would be a much better base for a free software mobile operating system than a current linux distribution. lots of engineering work and experience went into making it, both on the technical sides and in the UX, with lots and lots of feedback. it has largely solved permissions, inter-app communication, power saving, things like these, and I mean all in the AOSP project, forgetting about the proprietary google mobile services.
    not everything is perfect, lots could be improved, and there are things we don't like, like how app background activity is handled is not too transparent and neither customizable, etc, but those would be much easier to fix and maintain then reimplementing everything. hardware drivers are a problem, but it is anyway, and with android we at least have a working system with which reverse engineers can analyze the drivers in operation. certainly android is not the cleanest codebase but its not so bad either to warrant throwing it away. in the parts of the code I looked over the years, it's quite organized, but of course I have only seen very little.

  • permalink
  • fedilink
  • source
  • parent