Live data from Hacker News

In 2024, please switch to Firefox

roytanck.com

271–280 of 850 posts

Re: In 2024, please switch to Firefox

#271
Chrome became defacto because of techies and now techies are actively destroying the web by no longer swapping people to firefox, I guess it doesn't matter anymore, activism in general is dead, people just sit and let us all enter into a dystopia willingly.

Cannot wait until unskippable ads even with "Premium" are a thing, just like cable, and our community will have been complicit in enabling it

Re: In 2024, please switch to Firefox

#272

Earlier quoted context omitted.

The only site I've found behaves terribly in Firefox is LinkedIn. Weird pauses on page load that lock the whole browser (not just the tab) for like 5-10 seconds. No idea what they're doing to make this happen, but it's odd. Which is, well, fine, because LinkedIn is mostly a dumpster anyways.

This prompted me to check LinkedIn after months of having it parked in a tab and it worked with no problems. When I have problems with a site it's usually because I'm blocking most JavaScript with uMatrix and I have to find the correct combination of scripts to make the site work for me without having to give away my soul to the gods of tracking. As a software developer, it's been years since a customer told me that…

Also checked LinkedIn, no issues in FF on a mid-2014 mbp.

Re: In 2024, please switch to Firefox

#274
Nowadays when a site functions in Chrome/Safari but not in Firefox, what are the common culprits?

Usage of experimental Web APIs? Specific CSS properties? Deprecated features still supported by Chrome/Safari for backward compatibility?

I ask because I'm wondering if it's possible for an extension/userjs to, if not polyfill, at least detect and warn users about attempts to use such features. Nowadays when a site doesn't appear to work correctly in Firefox I reopen it in Chrome, but this is a not-insignificant source of time-waste because about half of time I find either that the site is working as the developer intended, or that the site doesn't work in Chrome either. Having some overt indication (visible without having to open devtools) that unsupported browser features are being accessed could be very helpful here for reducing user uncertainty.

Relatedly: I'm glad Firefox is planning to add support for IE's non-standard (but widely used ime) CSS zoom property: https://bugzilla.mozilla.org/show_bug.cgi?id=390936

Re: In 2024, please switch to Firefox

#275
post #79

As someone in the Apple ecosystem, Firefox is not a very compelling alternative. I've certainly tried: Firefox Focus was my main iOS browser for a few years (I know it's Webkit-based) and I've tried switching on desktop as well. On desktop, various Firefox updates would change my settings subtly and nag me about features I had no interest in. On top of that, it was simply a slower browser, both with DOM manipulation…

> I've certainly tried: Firefox Focus was my main iOS browser for a few years (I know it's Webkit-based)

TL;DR The truth is, no one has ever used Firefox or Chrome on iOS.

You say you know it's webkit based... but the entire engine for any browser on iOS is Safari, not merely webkit based. Apple doesn't have a policy of "your browser must be derived from webkit" they have a policy of forcing browsers to use the literal same engine built into iOS that Safari is using - i.e you are just using Safari with a different UI, there is only one browser engine on iOS.

This is an annoying detail to have to repetitively explain to people, and Apple benefits from this blurring of the lines in the army of users defending them for browser diversity. Honestly, if i had an iOS device I would use the Safari app - and as a web dev and a user I fucking hate Safari, but what's the point in using a different UI, they are all the Safari engine, the main browsing experience is by definition the exact same.

Re: In 2024, please switch to Firefox

#277

I switched back to firefox last year and haven't looked back. I still use chrome on another laptop sometimes, the performance difference from my human perspective is literally zero. These days, it's much more common for me to encounter a website that works in firefox but not chrome than the other way around. I actually switched for good when I had to use firefox to file my taxes, because the IRS free self-file site w…

Chrome is the new IE6

Re: In 2024, please switch to Firefox

#278

Anyone else remember Mitchell Baker (Firefox CEO) calling for more than deplatforming? https://blog.mozilla.org/en/mozilla/we-need-more-than-deplat...

All in all we need more of this, rather than the bland milquetoast garbage we are spoonfed by media. The insurrection attempt is a huge deal that is being treated with kid gloves. What in Baker's proposal specifically do you disagree with? I'll copy/paste them here:

- Reveal who is paying for advertisements, how much they are paying and who is being targeted.

- Commit to meaningful transparency of platform algorithms so we know how and what content is being amplified, to whom, and the associated impact.

- Turn on by default the tools to amplify factual voices over disinformation.

- Work with independent researchers to facilitate in-depth studies of the platforms’ impact on people and our societies, and what we can do to improve things.

Re: In 2024, please switch to Firefox

#280
I've been using Firefox since it was still called Phoenix.

It's amazing how we find ourselves in the same situation we did 20 years ago, at the mercy of a tech behemoth dominating how to access the Web, with the same Mozilla being the last man standing in the way of a true monopoly.

I may have some reservations about decisions and actions from Mozilla these past few years, but they do what they must to survive, and still provide a net benefit to our world.

Post reply on HN