741–750 of 1001 posts
Earlier quoted context omitted.
It's like Google found developer goodwill burdensome, and decided to pack it all up into container trucks and ship it all to Microsoft.
I agree. It is truly unbelievable. Same with user goodwill. Microsoft is vaccuuming it all up. Meanwhile Microsoft is making tons of great moves to get devs and users back on their side.
It is so clear to me that we need to support and promote mozilla and Firefox. They're not perfect, but they, wikipedia, eff, archive.org (who else?) are such an important part of the Internet guardianship in the face of the monopolies, that it's our duty to support them. Doesn't hurt that Firefox is actually a great product.
> Doesn't hurt that Firefox is actually a great product. Arguably. On these threads there is always a handful of complaints about the state of Firefox, mostly on macOS. On my machine, I can’t even launch Firefox in headless mode without the fans turning on, which never happened on Chrome. While I haven’t benchmarked it, for normal browsing it does feel slower than Crome. But what kills it for me is their crippled App…
I don't understand why Mac users use Chrome. Safari seems to be out of fashion: people just assume that it should not be used for some reason, even though it is actually a great browser. I use Safari for both my own browsing and for development (a fairly large ClojureScript application), and it is by far the best browser on the platform by all measures (speed first and foremost). The only place where Safari falls sho…
However as I posted in another comment, Safari is the new IE when it comes to bugs and standards compliance.
Here's an example that broke many many sites that use OAuth2 Auth Code Flow for login (including the main UI portal my company provides clients): https://bugs.webkit.org/show_bug.cgi?id=194906
This was also an issue in iOS, and since Apple doesn't let any other browsers actually use their own rendering engine on that platform (they're just wrappers around Safari's guts) this was broken for all iPhone users no matter the browser.
This is just one example. There's been numerous other issues such as disabling third party cookies by default.
I can only surmise that Mac users use Chrome/FF because the internet just _works better_ when they do.
Earlier quoted context omitted.
At least Microsoft managed to open source the guts of Chakra before they shutdown Edge. V8 hegemony might be worse for the internet given Node and Electron than Chrome alone.
Is there an Electron backing that doesn't use Chromium?
There was a port of node that used Chakra instead of v8, but I don't think it's maintained. And this is only one piece of the puzzle.. Electron also relies Chromium itself for rendering so this would probably be a pretty sizable effort.
Earlier quoted context omitted.
I’m a developer and power user, I switched to Firefox months ago. What is making difficult to switch? I found equivalent for all my plugins so far.
What is the equivalent for one tab? It is technically simple enough that I could develop one one my own, except I remember firefox extensions to be an unbelievable pain to install back in the day.
Installing is one click - as simple as the chrome web store.
If you want the ability to unload tabs, firefox struggles with it. The best addon is https://addons.mozilla.org/en-US/firefox/addon/unload-tabs/ but it admits that it is buggy. Haven't tried it though.
Earlier quoted context omitted.
In my opinion, profiles are useful for separating "who I am." Whether that's my personal life and my professional life, or if it's me or my spouse using the same computer. Containers are useful for separating "who I am to my providers." As far as Facebook is concerned, I am a Facebook user, but I don't use Amazon or Google. But Amazon thinks I'm an Amazon user that doesn't use Facebook or Google. You can accomplish t…
You can definitely have two profiles open simultaneously - on MacOS, this is achieved with “open -n Firefox.app --args -P [profile name]”; on Windows, “firefox -no-remote -P [profile name]”. Admittedly, that should _really_ be exposed in the UI somehow, but at least it means you can wrap up the command in a handy desktop shortcut (e.g. one that says “my Firefox” and one that says “her Firefox”).
Earlier quoted context omitted.
Luckily for us, there's antitrust law. This isn't really possible: Reproduction steps: 1. Check that Google search is working by opening Chrome, navigating to www.google.com, and searching for any term (such as the name of a newspaper and clicking the link to verify that search works as expected.) 2. Open firefox.com and navigate to www.google.com You will receive a message: "It looks like you have Chrome installed!…
Assuming antitrust law is enforced...
I don't understand why Mac users use Chrome. Safari seems to be out of fashion: people just assume that it should not be used for some reason, even though it is actually a great browser. I use Safari for both my own browsing and for development (a fairly large ClojureScript application), and it is by far the best browser on the platform by all measures (speed first and foremost). The only place where Safari falls sho…
Earlier quoted context omitted.
> Just look at YouTube denying Chromium-based Edge the new redesigned experience for absolutely zero reason. The reason is almost certainly a new user agent (compared to non-Chromium Edge) that YouTube didn't expect. Chromium-based Edge is still not stable, and therefore, not properly supported by YouTube. I don't have time to test this, but I'm willing to bet that you'd get the same result by using any indie browser…
This is a rediculous justification. Websites should not be coded to a whitelist of browsers.
It depends on what you choose as your choice of technology, if you choose web components then you really can only really offer that same experience to users that have a browser that supports that API natively (without polyfills) which old Edge did not do.
My understanding of this situation with yt was that our server side detection code was wrong based on an update in edge (or our UA management), and we don't do feature detection in the client because it is too slow... So we send people to the older version.