‹ BackHN Continuity

Thread

Android 17 is the first since 3.x to add new APIs without releasing to the AOSP

1180 points · 723 comments · theanonymousone

  1. wps · · focus · HN ↗
    The amount of roadblocks Google is putting up for GrapheneOS is just ridiculous. None of their decisions make any sense, from the delayed source patches upstream, to the embargos, attestation issues, etc. Google simply regrets android being open source.
    1. godelski · · focus · HN ↗
      I hope people remember this when advocating for chromium. Just because it is open source doesn't mean they don't control it. We need to start the long process of hard forking now or turn to alternatives like Firefox as a new foundation.

        > Google simply regrets android being open source.
      
      Android wouldn't be what it is if it wasn't open source. With all the work from outside Google. The same is true chrome.

      But they won't learn that on their own. They are breaking the deals. So we move. We force their hand

      1. cecexacjrgec · · focus · HN ↗
        > or turn to alternatives like Firefox as a new foundation.

        With the way Firefox is heading, that might not be the best idea. Nowadays Mozilla seem more focused on riding the AI-hype wave than actually making an excellent browser people want to actually use.

        1. II2II · · focus · HN ↗
          It is sad to see Firefox riding various hype trains over the years, but I can't really blame them. Miss the wrong train, and you fall behind and may not be able to catch up. Miss the train to nowhere, and you are only wasting resources.

          As for the excellent browser that people want, that raises the question of what people want. There are likely as many answers as people.

          1. cecexacjrgec · · focus · HN ↗
            Yeah. It’s a tough balance to achieve but that’s the situation we’re in right now so Mozilla really ought to step up (and I totally wish they would).

            My biggest pain point at the moment (entirely subjective mind you) is not even the AI nonsense, but how disjointed and alien the Firefox UX and general feel is to Apple platforms (what I use, at the moment). I don’t want Firefox to mirror Safari 1:1 but I do want the Firefox UI and UX to feel polished, well thought out and thoroughly in line with system HIG specs—given that I spend a lot of time in a browser, it shouldn’t feel like a stranger in a strange land amidst my other desktop applications.

            Aggressive UI improvements would go a long way to restore some faith in the incandescent fox‘ mission—at least for me.

            1. josephg · · focus · HN ↗
              What aspects feel foreign on macOS? The Firefox preferences for sure. Anything else?
              1. weikju · · focus · HN ↗
                Tab close buttons are on the right (windows style) instead of on the left (macOS style), for one.
                1. odo1242 · · focus · HN ↗
                  I mean, it’s the same on every browser except Safari
                  1. weikju · · focus · HN ↗
                    Orion also does it right.

                    Every other browser aren’t using macOS native UI therefore are wrong in this environment. But right on their own in being the same everywhere.

                    1. cecexacjrgec · · focus · HN ↗
                      Unfortunately “being the same everywhere” only works if your application is distinctive enough in functionality that it can’t be anything else but itself. Firefox is just a browser. Safari is also a browser. Chrome is also a browser. And none of these apps are more important or relevant than the operating system they are working under.

                      If my OS says windows and tabs close on the left, then I expect every single app to be a good platform citizen and not make me relearn default controls just to operate simple functions. Windows and tabs close on the left. End of story.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.