Thread

1. wps · 1789760710 · 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 · 1789763541 · 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. StilesCrisis · 1789766362 · focus · HN ↗

         Hard forking doesn't solve the problem of closed source.

         If the goal of a hard fork is "the community will invest equal resources that Google does today" then you wildly underestimate how many engineers work on Chrome.

         1. floxy · 1789781514 · focus · HN ↗

            >wildly underestimate how many engineers work on Chrome.

            It is completely insane how many people work on Chrome. It seems like it is time to deprecate web browsers and do something different. Like you get a frame-buffer to draw on with something like a wasm vm. Web pages get replaced by programs (which they essentially are anyway). Get rid of 99.9% of the cruft that has accumulated over the decades in browsers. If you want to have some of that cruft, that is a library you have to send.

            1. kjs3 · 1789782869 · focus · HN ↗

               Or go the other way and make web pages not programs at all, like they originally were. Unfortunately, just communicating information isn't cool, doesn't monetize, and certainly doesn't get clicks.

               1. mapontosevenths · 1789794788 · focus · HN ↗

                  The biggest mistake the web ever made was leaving it up to to the website to choose how content renders.

                  It should be the users choice how their browser renders, it's their damn browser. Instead, browsers are built to follow standards that mostly favor the developers preferences above those of the person who actually own the device rendering it.

                  The modern web is user hostile by design.

                  1. Xirdus · 1789807197 · focus · HN ↗

                     If a web browser allows images, then the website always has full control over how content renders. It's the default. HTML and related standards are trying to persuade developers to cede some of that control in the name of accessibility, user choice, searchability, device compatibility etc. that all-image websites lack. But this can only succeed if the developers still can do everything they want to. If they can't, then they'll fall back to images and everyone loses.

                     1. microtonal · 1789820613 · focus · HN ↗

                        Yep, in the old days, a lot of websites used image maps (so that clicking a part of the image would go to another page).

Unofficial Hacker News client; not affiliated with Y Combinator.