flatlined

joined 1 year ago
[–] flatlined@lemmy.dbzer0.com 0 points 3 weeks ago (1 children)

No but you see we at Google aren't locking down sideloading. It's the individual app developers. With the api we gave them for that express purpose. Totally not us locking stuff down though, so EU please ignore us trying to indirectly close doors in our walled garden?

[–] flatlined@lemmy.dbzer0.com 3 points 1 month ago

Which (pr nightmare aside) I wouldn't be against. It's not gonna fly, people are accustomed to 'free' browsers to the point they'd balk at the idea. Even if they weren't most would take a free chromium based browser or Firefox fork over a paid alternative that doesn't give them anything extra. But browsers are massive pieces of tech, they need a lot of dev time, and the money needs to come from somewhere, just relying on volunteers won't cut it.

Mozilla has been looking for sources of funding for years, sometimes in ways that are their own type of pr nightmare and sometimes in ways I'm not thrilled by, but I get their predicament. I wish there would be (more) state funding. EU, US. Whatever. Much like governments should invest in public transit we should invest in critical software infra.

I also wish Google's other branches were divorced from their browser dev branch. The stranglehold on the web given to Google by chrome is a huge part of the problem.

[–] flatlined@lemmy.dbzer0.com 0 points 2 months ago

It's a variation on the old saw of "how much is the difference between a million and a billion? About a billion". Once numbers become so big, it's hard to grasp the relative sizes. That said, I'm also interested in a more comprehensive breakdown. Seeing who are impacted, how much and where.