Live data from Hacker News

Google Chrome Arrives on ARM64 Linux, Widevine DRM Included

omgubuntu.co.uk

31–40 of 50 posts

Re: Google Chrome Arrives on ARM64 Linux, Widevine DRM Included

#31
post #6

Earlier quoted context omitted.

Mozilla making choices specifically to try to "keep up" with Chrome has objectively failed: Firefox's marketshare has plunged so far that it's getting harder to keep using it on the web, as developers simply stop testing or caring much if it works with their site. I think this is because simply chasing Chrome didn't have the desired effect anyway. By doing so, Mozilla hurt Firefox by gradually reducing what different…

> Firefox's marketshare has plunged so far that it's getting harder to keep using it on the web any examples? i only use firefox, including for work, as well as encourage all of my students to use it, and i cant think of any sites that dont work. if anything, i would say its sort of the opposite (getting easier to use). some microsoft websites were wonky ~5 years ago, but now all seem to work perfectly in firefox.

A lot of websites will "work" because they added Firefox workarounds. But to a Chromium or Safari user, it might as well be called a "degraded" mode.

A lot of video-conferencing websites work that way as Firefox has had a lot of issues keeping up with the WebRTC standard evolution that power them for example.

Re: Google Chrome Arrives on ARM64 Linux, Widevine DRM Included

#32
post #21

Earlier quoted context omitted.

> Simple: allow those users to be lost to preserve the product. Lose the users lose the funding. Firefox can't live out of HN as its sole userbase. Have you checked how much it costs to build and maintain a modern browser? Plenty of users who have no money for TV or consoles, watch it on their laptop on low quality. I am one of those who watches Netflix on Linux Firefox :) This isn't just any risk. It's an existentia…

Yes I am asking them to have principles. I'm sorry this is such an insane concept to understand or appreciate. Maybe the next Mozilla will understand that having principles is not optional.

>Maybe the next Mozilla will understand that having principles is not optional.

But what does "having principles" translate to? Focusing on the EME issue, how many people are going to be like "humpf, firefox added EME so I'm going to use chrome instead!"? Is that small slice of the user base even worth keeping? If they're going to be incensed by random issues like this, they're probably not worth the trouble to cater to, or maybe they'll just flip flop between chrome and firefox (depending on what the latest outrage headline is) that there's not much point in catering to.

If you can't articulate specific benefits to "having principles", then you're not really interested in firefox winning, you just want it to die a martyr.

Re: Google Chrome Arrives on ARM64 Linux, Widevine DRM Included

#33
post #9
post #8

Earlier quoted context omitted.

>I think this is because simply chasing Chrome didn't have the desired effect anyway. By doing so, Mozilla hurt Firefox by gradually reducing what differentiated it from Chrome in the first place, relegating it to be kind of just a worse Chrome that looks even weirder. That logic might work for firefox's product direction as a whole, but narrowly looking at the EME issue, what should have they done? If they didn't im…

Simple: allow those users to be lost to preserve the product. The entire Internet is not Netflix. Most Netflix users today don't even use their laptops or desktops for Netflix: they use it on their TVs, phones, video game consoles. Firefox is a bad way to use Netflix anyways. It doesn't support high resolutions because it has limited Widevine support anyways. It doesn't support Widevine l1 and never has. So... It is…

Yes, this is a no brainer. Whenever someone accesses NetFlix on a Firefox with no EME, just display a page which has a short description explaining why Firefox doesn't support EME ("EME is not included to protect your privacy as it allows websites to profile and identify you more easily") and provide a button to open Netflix either through a Netflix app or the pre-installed OS browser (Edge or Safari). Educate your users rather than treating everyone as dumb.

Or, reintroduce browser plugins (with permission based architecture).

Re: Google Chrome Arrives on ARM64 Linux, Widevine DRM Included

#34
post #9

Earlier quoted context omitted.

Simple: allow those users to be lost to preserve the product. The entire Internet is not Netflix. Most Netflix users today don't even use their laptops or desktops for Netflix: they use it on their TVs, phones, video game consoles. Firefox is a bad way to use Netflix anyways. It doesn't support high resolutions because it has limited Widevine support anyways. It doesn't support Widevine l1 and never has. So... It is…

Yes, this is a no brainer. Whenever someone accesses NetFlix on a Firefox with no EME, just display a page which has a short description explaining why Firefox doesn't support EME ( "EME is not included to protect your privacy as it allows websites to profile and identify you more easily" ) and provide a button to open Netflix either through a Netflix app or the pre-installed OS browser (Edge or Safari). Educate your…

>and provide a button to open Netflix either through a Netflix app or the pre-installed OS browser (Edge or Safari). Educate your users rather than treating everyone as dumb.

I think it's pretty reasonable to assume the overwhelming majority of users are going to install the app or use chrome. The average internet user is someone who thinks facebook and tiktok is spying on them but uses those apps anyways. What makes you think they'd take a stand on netfilx, of all things?

>Or, reintroduce browser plugins (with permission based architecture).

That's literally what EME is, with better sandboxing.

Re: Google Chrome Arrives on ARM64 Linux, Widevine DRM Included

#35
post #22

Earlier quoted context omitted.

They can't pull it now because they don't have big enough marketshare. Gee I wonder why that didn't work out.

Surely not because they weren't pure enough. The browser market was always so big that pure alternatives were never with any advantage: on the contrary, they had more issue because they catered to a loud minority that can always push for a "you are not pure enough" narrative. Because who push for that just doesn't care (rightfully) to be mainstream. Thinking back at the actual history (and I lived it, having used Net…

> they had more issue because they catered to a loud minority that can always push for a "you are not pure enough" narrative. Because who push for that just doesn't care (rightfully) to be mainstream.

Discussing certain things on HN is like a portal into another dimension full of profoundly out-of-touch people who somehow think being contrarian to the technical nerd crowd is actually what being "in touch" means. How do you reckon Firefox actually gained popularity in the first place?

I don't think Firefox ever lived or died on "purity", but it sure as shit harmed its own image multiple times over the years in ways that have absolutely nothing to do with "catering to a loud minority". Like for example:

- Killing all of the extensions; extensions that once differentiated Firefox as a product became unusable or unavailable, like Vertical Tabs and NoScript. The Web Extension versions of these never worked as well. It killed off one thing that made Firefox "better" than Chrome. Did the vocal minority ask for this?

I fully understand that Web Extensions was done for technical reasons, but of all the paths forward it's hard to imagine this was actually the best one. Today, Firefox hardly offers any extensions Chromium-based browsers do not or can not, mainly because Firefox extensions got worse.

- The various over-reaching sponsorship deals. The Google Search one obviously drew plenty of scrutiny itself, but I think most people understood it as a necessity. The Looking Glass/Mr Robot advertisement controversy and its use of Firefox Studies as a vector for deploying unwanted code, on the other hand, absolutely hurt Firefox's image among power users (and some others, judging by press at the time). Hey maybe they should've consulted that vocal minority.

- The "Terms of Use" update. It is still to this day not clear why this was necessary, but it was bad PR that spread throughout the Internet, especially Twitter and Reddit.

- A lot of updates that made user customization worse or more limited, bringing it much more in-line with Chrome. Mobile Firefox doesn't even let you use about:config anymore, and still only allows whitelisted extensions as far as I know.

- The new AI push. Now when you hold down the mouse button on a link you get a "link preview". Nobody asked if you wanted this feature, it's just there now. The previews are almost unilaterally useless, too, just to add insult to injury.

They may very well have lost a lot of their marketshare for other reasons, but because of a lot of these decisions there is little reason for a user to not choose Chrome.

Can they trust Mozilla more? Well, their track record isn't fantastic, all things considered.

Can Firefox do anything Chrome can't? There's a couple things but Chrome does a lot more things that Firefox can't do than vice versa.

Is Firefox faster or more efficient than Chrome? That one was lost a long time ago.

Is Firefox more secure than Chrome? Given that it still lacks a lot of the sandboxing technologies Chrome has, I'd venture to guess "no".

Mozilla's problem isn't that they weren't "pure" enough, but it absolutely is a problem that they seemed to really lack any principles at all and just blindly chase trends and Chrome to try to keep up. This really has nothing to do with purity and is exactly the opposite of caring about a vocal minority. It's just that chasing Chrome was always a losing strategy from the start.

The vocal minority, of course, is the Firefox evangelists. Upsetting and ignoring the people who evangelize your products isn't usually your best move...

> Thinking back at the actual history (and I lived it, having used Netscape Navigator, the Mozilla Suite and Phoenix 0.1), my view is that when Firefox was winning marketshare in Windows-land over IE, the release of Chrome and Google behind it basically killed (slowly) its momentum [1]. Even if the momentum was surely paid for by Google who was the default search engine in Firefox and paid millions to Mozilla for it.

I also lived through the rise of Firefox, FWIW; the first browser I ever used was Netscape Navigator 4.0.

How did Firefox manage to spread against the pre-installed Internet Explorer browser? Aside from that splashy NYT ad, I would assert much of it came from word-of-mouth.

Chrome probably spread a lot just by virtue of being pre-installed on a lot of computers and phones, but that's also how Internet Explorer spread. At some point, people stopped installing Firefox on their new machines, and it's worth interrogating why.

Re: Google Chrome Arrives on ARM64 Linux, Widevine DRM Included

#36
post #32
post #21

Earlier quoted context omitted.

Yes I am asking them to have principles. I'm sorry this is such an insane concept to understand or appreciate. Maybe the next Mozilla will understand that having principles is not optional.

>Maybe the next Mozilla will understand that having principles is not optional. But what does "having principles" translate to? Focusing on the EME issue, how many people are going to be like "humpf, firefox added EME so I'm going to use chrome instead!"? Is that small slice of the user base even worth keeping? If they're going to be incensed by random issues like this, they're probably not worth the trouble to cater…

> But what does "having principles" translate to? Focusing on the EME issue, how many people are going to be like "humpf, firefox added EME so I'm going to use chrome instead!"? Is that small slice of the user base even worth keeping? If they're going to be incensed by random issues like this, they're probably not worth the trouble to cater to, or maybe they'll just flip flop between chrome and firefox (depending on what the latest outrage headline is) that there's not much point in catering to.

> If you can't articulate specific benefits to "having principles", then you're not really interested in firefox winning, you just want it to die a martyr.

You've got it backwards. It's not that people use Chrome in retaliation for Firefox having zero principles, it's that people stop caring to install Firefox because there's no clear reason to keep using it.

Having no principles itself eventually loses you a small minority of users... and those were your core supporters and evangelists. It is not a huge number of people, but it's not good when your base of supporters is rotting from the inside-out.

Re: Google Chrome Arrives on ARM64 Linux, Widevine DRM Included

#37
post #28

Using Chrome on Linux is a big mistake because your session is much more likely to get flagged as a bot.

which is especially silly because every half-competent scraper knows this, and will just lie - it's so easy. but I have seen this happen as well, trying to legitimately use Chrome on Linux

Re: Google Chrome Arrives on ARM64 Linux, Widevine DRM Included

#38
post #36
post #32

Earlier quoted context omitted.

>Maybe the next Mozilla will understand that having principles is not optional. But what does "having principles" translate to? Focusing on the EME issue, how many people are going to be like "humpf, firefox added EME so I'm going to use chrome instead!"? Is that small slice of the user base even worth keeping? If they're going to be incensed by random issues like this, they're probably not worth the trouble to cater…

> But what does "having principles" translate to? Focusing on the EME issue, how many people are going to be like "humpf, firefox added EME so I'm going to use chrome instead!"? Is that small slice of the user base even worth keeping? If they're going to be incensed by random issues like this, they're probably not worth the trouble to cater to, or maybe they'll just flip flop between chrome and firefox (depending on…

> it's that people stop caring to install Firefox because there's no clear reason to keep using it.

Who's going to switch to chrome (or not install firefox, next time they install a browser), even though that also has DRM, and unlike firefox's EME implementation, can't be disabled and is even more invasive? Either they care about DRM/EME and therefore they'll choose the least bad option, or it's all posturing.

Re: Google Chrome Arrives on ARM64 Linux, Widevine DRM Included

#39
post #31

Earlier quoted context omitted.

> Firefox's marketshare has plunged so far that it's getting harder to keep using it on the web any examples? i only use firefox, including for work, as well as encourage all of my students to use it, and i cant think of any sites that dont work. if anything, i would say its sort of the opposite (getting easier to use). some microsoft websites were wonky ~5 years ago, but now all seem to work perfectly in firefox.

A lot of websites will "work" because they added Firefox workarounds. But to a Chromium or Safari user, it might as well be called a "degraded" mode. A lot of video-conferencing websites work that way as Firefox has had a lot of issues keeping up with the WebRTC standard evolution that power them for example.

A lot of video-conferencing websites work that way because Chrome shipped a pre-standardization form ("Plan B") of WebRTC, it got a lot of uptake, and then they refused to unship it when the final standard came out with an alternative way of doing the same thing. It took a decade to finally give in and unship the nonstandard path.

https://groups.google.com/a/chromium.org/g/blink-dev/c/IY2am...

https://webrtchacks.com/is-everyone-switching-to-unified-pla...

Then they did it again with MediaStreamTrackProcessor and MediaStreamTrackGenerator.

Then they did it again with Insertable Streams, which is still an issue for interoperable E2EE (Firefox ships a standardized variant).

If you think of websites as running on a standardized platform, then the workarounds are for Chrome, not Firefox. They include, and default to, code that calls unspecified APIs and then the ones that care autodetect when that doesn't work and fall back to APIs with actual agreed-upon specs.

Describing this as "Firefox has had a lot of issues keeping up with the WebRTC standard evolution" is... inaccurate. My impression is that there have been, and continue to be, areas where this could be leveled as a fair complaint. But refusing to implement rejected proposals because they had too much uptake already? That's the only way to keep the web platform's foundation solid.

Re: Google Chrome Arrives on ARM64 Linux, Widevine DRM Included

#40
post #27
post #6

Earlier quoted context omitted.

Mozilla making choices specifically to try to "keep up" with Chrome has objectively failed: Firefox's marketshare has plunged so far that it's getting harder to keep using it on the web, as developers simply stop testing or caring much if it works with their site. I think this is because simply chasing Chrome didn't have the desired effect anyway. By doing so, Mozilla hurt Firefox by gradually reducing what different…

Firefox should've gone the same route as Internet Explorer and forked Chromium. Firefox could focus its energies on creating features that are different instead of recreating the same ones.

Great, so any minor bug in Chromium's implementation of a spec is going to be forever embedded in the spec as the only allowed way to do it?

Multiple independent implementations are the only practical way to ensure a self-consistent and reasonable platform. Sure, it's not a disaster in an area where people can recompile all their code when something in the platform (eg the compiler) changes, but that's now how the web works.

Post reply on HN