zlacker

[parent] [thread] 87 comments
1. onli+(OP)[view] [source] 2023-01-24 11:28:51
Fighting Apple's monopoly behaviour around Safari is not fighting for chrome.

Since you asked, Firefox is the browser to use if you do not want chrome.

replies(6): >>kristi+P3 >>leland+A6 >>kivle+ca >>boxed+Po >>Gorbze+vs >>veheme+z71
2. kristi+P3[view] [source] 2023-01-24 12:00:33
>>onli+(OP)
As a Firefox user who is very upset with Apple for (clearly intentionally) lacking support for PWA features, I am still happy that Safari exists as a counter-weight to Chrome. Any contribution counts.
replies(4): >>ThatMe+E5 >>kllrno+zy >>runjak+GU >>musica+3E2
◧◩
3. ThatMe+E5[view] [source] [discussion] 2023-01-24 12:15:26
>>kristi+P3
As a Firefox user on Linux I'm about to switch honestly. The browser is in a terrible state on Linux in terms of performance.

There is video playback on without fan noise (Chromium) or a very audible fan noise on Firefox (Notebook & Steam Deck + Fedora/Pop/Arch/Ubuntu) => More use of power resulting in less time for me.

Switching to Linux resulting in me ditching my forever browser Firefox is something I would not have guessed.

replies(7): >>capabl+C9 >>jacoop+ge >>jadbox+Hh >>sbaidd+gr >>drdebu+pz >>josefx+bM >>encryp+MW
4. leland+A6[view] [source] 2023-01-24 12:20:55
>>onli+(OP)
https://gs.statcounter.com/

Firefox is not a serious competitor at this point and its tiny 4% of the market has already slipped to 3% in the last year.

That’s inching close to the “can we please drop IE11” sort of numbers from some years ago.

replies(4): >>Merely+S6 >>rypska+ib >>pmontr+jg >>kibwen+oD
◧◩
5. Merely+S6[view] [source] [discussion] 2023-01-24 12:23:16
>>leland+A6
Are you suggesting that people shouldn't use it since it has a small market share, and thus should allow it to get smaller until it dies out?
replies(3): >>leland+p7 >>Karuna+Zd >>uoaei+Z21
◧◩◪
6. leland+p7[view] [source] [discussion] 2023-01-24 12:28:21
>>Merely+S6
Moreso that Safari truly is the only bastion against Chrome’s hegemony.
replies(2): >>mtomwe+2a >>postal+DE
◧◩◪
7. capabl+C9[view] [source] [discussion] 2023-01-24 12:43:32
>>ThatMe+E5
You might want to check out that it's using hardware acceleration properly, and that's it's configured correctly to use wayland if you're on wayland.

Personally, I bounce between macOS, Windows and Linux (mostly Linux, with Wayland), between Chrome, Edge, Firefox, Safari (mostly Firefox), and also between laptops/desktops and Firefox on Linux is consistently the fastest one with the least amount of crashes for me. Also the combination that lets me get the most battery life out of my laptop.

replies(2): >>FpUser+4b >>Terret+ph
◧◩◪◨
8. mtomwe+2a[view] [source] [discussion] 2023-01-24 12:46:45
>>leland+p7
Safari is not competing. It only runs on MacOS and iOS. It doesn't compete on Linux, Windows or Android.

- It comes last out of the three major browser engines in feature support. - It has the most number of bugs out of the three engines. - It has the worst support for Web Apps.

Apple has deprived the Safari/Webkit team of funding for the past decade.

Safari places no competitive pressure on chrome, and has deprived Mozilla and thus Firefox of 100's of millions of dollars in search engine revenue. Apple has done untold damage to the web and this needs to be fixed.

replies(4): >>rvz+rf >>forget+Eh >>Klonoa+n71 >>robert+3a1
9. kivle+ca[view] [source] 2023-01-24 12:47:48
>>onli+(OP)
I tried to switch to Firefox as my main browser, but sadly the blocker for me was the absolutely horrible battery life on my Macbook Pro M1. It's like it's continuously running a spinning loop or something. It reduced my battery life to somewhere between 4 to 6 hours. I have since switched to Vivaldi (which is based on Chromium unfortunately), but I will probably switch back to Firefox if those battery issues are ever resolved.
replies(2): >>gls2ro+6A >>kitsun+d61
◧◩◪◨
10. FpUser+4b[view] [source] [discussion] 2023-01-24 12:54:50
>>capabl+C9
>"You might want to check out that it's using hardware acceleration properly, and that's it's configured correctly to use wayland if you're on wayland."

Maybe it should be browser's task to do it. As a user I just do not want to waste my time on things like that unless they're vital. In this case I'll just use different browser.

replies(4): >>nicobu+If >>TillE+zs >>capabl+Fs >>zamale+vP
◧◩
11. rypska+ib[view] [source] [discussion] 2023-01-24 12:56:36
>>leland+A6
Statcounter is in the list[0] firefox uses to block trackers, it also seems like Edge use the same list [1], so the 3% is more FF-users who are not using the build in tracking protection

[0]https://github.com/disconnectme/disconnect-tracking-protecti... [1]https://disconnect.me/trackerprotection#trackers-we-block

replies(2): >>leland+at >>jefftk+5S
◧◩◪
12. Karuna+Zd[view] [source] [discussion] 2023-01-24 13:15:55
>>Merely+S6
As it becomes more of a niche, also-ran browser, you can expect its quality (and so, its security) to fall as well.

The "use an inferior tool for philosophical reasons" mindset is already pretty unconvincing for me. A chromium fork maintained by a pro-user, pro-privacy team is the best of both worlds and doesn't expose you to Mozilla's fad-chasing.

replies(2): >>Keegs+og >>Lalaba+ih
◧◩◪
13. jacoop+ge[view] [source] [discussion] 2023-01-24 13:18:14
>>ThatMe+E5
To add to that, Firefox sandboxing on Linux is awful.

https://madaidans-insecurities.github.io/firefox-chromium.ht...

◧◩◪◨⬒
14. rvz+rf[view] [source] [discussion] 2023-01-24 13:26:33
>>mtomwe+2a
Firefox is almost no where to be found and hardly has anything to bring to fight against Chrome [0]. In fact, Mozilla is on life support with Google's money with the Mozilla CEO being the one laughing all the way to the bank as Firefox continues to be irrelevant.

Safari (WebKit) is the only one competing against the Chrome ecosystem, especially on mobile devices market. The EU Digital Markets Act will just declare Chrome the winner and will increase Chrome's dominance and will make Mozilla even more irrelevant.

[0] https://gs.statcounter.com/

◧◩◪◨⬒
15. nicobu+If[view] [source] [discussion] 2023-01-24 13:27:48
>>FpUser+4b
> Maybe it should be browser's task to do it.

Unfortunately you don't really get that luxury if you use Linux.

◧◩
16. pmontr+jg[view] [source] [discussion] 2023-01-24 13:31:29
>>leland+A6
Statcounter has no chance to see my Firefox browsers on Linux and Android, because of uBlock Origin and Blockada.

Maybe they don't see as many Chrome browsers too, in percent. Maybe Firefox users are not the ones who block more tracking, who knows.

◧◩◪◨
17. Keegs+og[view] [source] [discussion] 2023-01-24 13:31:53
>>Karuna+Zd
Firefox is not an “inferior tool.” Its cookie segregation and CSS styling feature are not found in Chrome. I don’t use Firefox for moral reasons, I use it because it’s better.
replies(1): >>iggldi+Zo
◧◩◪◨
18. Lalaba+ih[view] [source] [discussion] 2023-01-24 13:36:49
>>Karuna+Zd
This is assuming that their funding is dependent on their share of browser use, or that Mozilla would get bored of Firefox if it stays at a lower share, and move on to other projects.

These assumptions would be true of a for-profit entity like Google, Apple, Microsoft, but it's not as directly applicable to Mozilla.

replies(1): >>Karuna+wj
◧◩◪◨
19. Terret+ph[view] [source] [discussion] 2023-01-24 13:37:40
>>capabl+C9
> Firefox on Linux ... the combination that lets me get the most battery life out of my laptop.

If you've managed to get battery life from Linux and Firefox even remotely near default fresh install of MacOS and Safari, you should write that up and post the link to it on HN.

replies(1): >>capabl+Qr
◧◩◪◨⬒
20. forget+Eh[view] [source] [discussion] 2023-01-24 13:39:18
>>mtomwe+2a
The point is that, even with all those flaws, developers have to target at least two browsers instead of just building for Chrome.

The force keeping Safari afloat is not the one keeping Firefox down, the problem is that Firefox has nothing to drive up its adoption. Telling people that they're "free" to use Firefox and see as the web is swallowed whole by Google with Chrome, like MS did with IE, is missing the point so badly.

replies(1): >>izacus+Gn
◧◩◪
21. jadbox+Hh[view] [source] [discussion] 2023-01-24 13:39:36
>>ThatMe+E5
While based on chrome without the privacy issues, I'd highly recommend Vivaldi browser (the company is also a worker co-op). They removed a lot of proprietary stuff too from the source.
◧◩◪◨⬒
22. Karuna+wj[view] [source] [discussion] 2023-01-24 13:51:24
>>Lalaba+ih
I think the first assumption holds. There is a (conspiracy?) theory that Google's funding of Mozilla is based on a desire to avoid antitrust scrutiny. If Firefox usage continues to tumble, it ceases to be a meaningful competitor and the funding might be safely discontinued without legal consequences.

Mozilla exists as it does today entirely due to Google's largess.

◧◩◪◨⬒⬓
23. izacus+Gn[view] [source] [discussion] 2023-01-24 14:11:42
>>forget+Eh
You're talking about lack of competition while defending corporate mandated lack of competition and undermining of the web. That's not how this works.
replies(1): >>forget+Io
◧◩◪◨⬒⬓⬔
24. forget+Io[view] [source] [discussion] 2023-01-24 14:17:28
>>izacus+Gn
Unless you think of another solution, when the "it" is the web, we have nothing else that works, because antitrust regulators won't come down hard enough on Google for leveraging its dominant position in search and mail to corner the browser market, and use it as an ad delivery platform.

Sent from my Firefox install.

25. boxed+Po[view] [source] 2023-01-24 14:18:08
>>onli+(OP)
I mean.. not intentionally maybe.
◧◩◪◨⬒
26. iggldi+Zo[view] [source] [discussion] 2023-01-24 14:19:13
>>Keegs+og
Plus much as I'm very much and definitively unhappy about a lot of directions and decisions taken by the Firefox developers, Chrome's (and Edge's, too) address bar search alone is a no-go – it's positively amnesiac and frequently (with no discernible rhyme or reason) doesn't return even pages I've recently visited and that are definitively still in my browser history (and it's not for lack of space to display the results, because often it returns no local results at all!).
replies(1): >>Karuna+tb1
◧◩◪
27. sbaidd+gr[view] [source] [discussion] 2023-01-24 14:29:58
>>ThatMe+E5
That's weird, I use Mac (x86) and Linux (x86 Debian) and Firefox works great on Linux but is unusable on Mac (at least it was two or so years ago when I last tried).

I have an nvidia card and non free drivers if that matters

replies(1): >>nicobu+zO
◧◩◪◨⬒
28. capabl+Qr[view] [source] [discussion] 2023-01-24 14:32:28
>>Terret+ph
My laptop only uses Windows and Linux, only Apple hardware I have is desktop. But makes sense that Safari gets best battery time on Apple laptops, friends with Apple laptops says the same.
replies(1): >>Firmwa+nG
29. Gorbze+vs[view] [source] 2023-01-24 14:35:16
>>onli+(OP)
It functionally is.

Many of those who have not learned from history are so anti-Apple (or possibly subpar webdevs) that they completely ignore the lessons we've previously learned about why browser monoculture is dangerous.

Even more worrisome, these people often ignorantly call Safari "the new IE", meaning they're aware of the history and problems and choose to pursue their own broken interpretation.

If these people will ignore a browser with 50% market share on mobile and 20% overall due to their own shortsightedness, clearly they're going to ignore Firefox or others hanging out in the single digits.

replies(1): >>error5+3D1
◧◩◪◨⬒
30. TillE+zs[view] [source] [discussion] 2023-01-24 14:35:42
>>FpUser+4b
Running Linux on a desktop pretty much guarantees that you have an endless parade of small problems to fix.

I really wish this weren't true, but the user experience has barely improved in the past 15-20 years. The specific problems may be different, but it's still the same struggle.

◧◩◪◨⬒
31. capabl+Fs[view] [source] [discussion] 2023-01-24 14:36:23
>>FpUser+4b
Takes time to migrate to a completely new display manager :) For now it's opt-in, in the future it'll obviously be default if you're on Wayland.

If you don't like bleeding edge, warts or sometimes unpolished experiences, might be better to go with Windows or macOS, no one would blame you.

replies(1): >>FpUser+jH
◧◩◪
32. leland+at[view] [source] [discussion] 2023-01-24 14:39:09
>>rypska+ib
Yeah, there’s no way to account for everyone. It’s probably not fair to assume there’s a huge amount of untracked users. And Mozilla cops to the continuing decline as well:

> “Looking back five years and looking at our market share and our own numbers that we publish, there's no denying the decline,” says Selena Deckelmann, senior vice president of Firefox

https://www.wired.com/story/firefox-mozilla-2022/

replies(1): >>onli+xw
◧◩◪◨
33. onli+xw[view] [source] [discussion] 2023-01-24 14:55:28
>>leland+at
If statcounter is in the list of blocked trackers, and trackers are blocked by default, then assuming there is a huge list of untracked users is only fair. Because it would be everyone not specifically disabling the tracking protection, which no one does. Statcounter would only count outdated FF installations that also do not use an adblocker (3% seems high for that, but not absurdly high).

But I'm not certain that this is the case. https://disconnect.me/trackerprotection claims to link to lists that show which trackers are only identified and which are identified and blocked, but those links just go to https://github.com/disconnectme/disconnect-tracking-protecti..., where I do not see such a distinction being made.

replies(2): >>blende+HK >>jefftk+oS
◧◩
34. kllrno+zy[view] [source] [discussion] 2023-01-24 15:05:18
>>kristi+P3
Nobody is arguing Safari shouldn't exist. They're arguing that Apple shouldn't get to force monopolize it on iOS even more aggressively than Microsoft was doing with IE 20 years ago.
replies(1): >>nradov+hF
◧◩◪
35. drdebu+pz[view] [source] [discussion] 2023-01-24 15:10:07
>>ThatMe+E5
Please try to resist. I bought an external battery, it's less convenient but if that's the cost of privacy then so be it. Supporting Mozilla/Firefox/Thunderbird is critical, some sites are now chrome-only, this is a nightmare. The battle for a free phone is already lost it seems as banks mandate google or iphone apps for 2FA and we don't have functional linux-only phones with browsing/email/mapping/sms/calls/photos that work reliably yet. I'm truly concerned we might loose the ability to use a linux desktop too: MS-Windows was required for many things in the past, these things are now possible on Linux, I'd hate to see Chrome become the next Windows.
◧◩
36. gls2ro+6A[view] [source] [discussion] 2023-01-24 15:12:42
>>kivle+ca
If Firefox will focus _everything_ on making FF on MacOS reduce their batter consumption to the minimum possible (less than Safari should be the goal) then I think this is the only _winning strategy_ for FF not going into irrelevance.

not sure it is also possible to compete on battery performance with Safari but that is the only one I see. Drop any other project, any initiative and just focus on this.

Why:

1. Because there is a big chunk of developers who code web on MacOS thus winning them means what they build will run on MacOS

2. Becoming default for this group of technical people means they will recommend it for their families and more important install it for their young kids laptops

3. Can do it with Google money :)

replies(1): >>kibwen+0C
◧◩◪
37. kibwen+0C[view] [source] [discussion] 2023-01-24 15:20:10
>>gls2ro+6A
There are approximately as many Firefox users are there are MacOS users, on the order of 200 million users. In fact, there are probably more Firefox users than MacOS users. Concrete numbers are hard to come by, but you have to take optimistic estimates of MacOS's userbase to match moderate estimates of Firefox's userbase. If Firefox is a global also-ran, then so is MacOS.
replies(2): >>gls2ro+eR >>dylan6+qS
◧◩
38. kibwen+oD[view] [source] [discussion] 2023-01-24 15:26:29
>>leland+A6
Does Firefox have a small market share compared to Chrome? Yes.

At the same time, Firefox has 200 million users. For perspective, that's just behind the population of Brazil, the world's seventh-most-populous country. It's hardly dead in absolute terms. It's hard to think of any open-source end-user application that's more widespread.

◧◩◪◨
39. postal+DE[view] [source] [discussion] 2023-01-24 15:32:10
>>leland+p7
Safari seems to rather build their own web then obey standards that both firefox and chrome are following. They are in many ways worse than chrome.
replies(4): >>kitsun+t41 >>robert+7a1 >>leland+8u1 >>dmitri+Si3
◧◩◪
40. nradov+hF[view] [source] [discussion] 2023-01-24 15:34:51
>>kllrno+zy
Microsoft was hardly even aggressive about leveraging their OS monopoly to promote their Internet Explorer browser. All they did was switch from selling it as a separate product to giving it away for free in order to crush Netscape. And Microsoft made IE the default handler for web links. But they never did anything to prevent users from installing third-party browsers on Windows.
replies(3): >>saiya-+xP >>angora+ZP >>kllrno+Jb1
◧◩◪◨⬒⬓
41. Firmwa+nG[view] [source] [discussion] 2023-01-24 15:39:27
>>capabl+Qr
I think it'd be worth reading how you got your Linux machine to behave itself though. Any time I've tried to run Linux on a laptop (even a supposedly well-supported Dell laptop) it's been a buggy mess.

Then again, Windows was even worse. It was constantly waking itself up in a cramped bag, where it would try to forcibly install updates, overheat, drain the entire battery, then shut down and need to charge for 30 minutes just to light up at all. At which point it would boot into the recovery menu since it botched an update and needed to try again.

replies(1): >>dylan6+3M
◧◩◪◨⬒⬓
42. FpUser+jH[view] [source] [discussion] 2023-01-24 15:42:56
>>capabl+Fs
I use both Windows and Linux. Linux runs on server and workstation class hardware dedicated for deployment mostly so the last thing I care about is what / how browsers run on those.
replies(1): >>capabl+JE2
◧◩◪◨⬒
43. blende+HK[view] [source] [discussion] 2023-01-24 15:55:01
>>onli+xw
> If statcounter is in the list of blocked trackers, and trackers are blocked by default, then assuming there is a huge list of untracked users is only fair.

Did we see a massive drop in Firefox users when tracking protection was introduced?

◧◩◪◨⬒⬓⬔
44. dylan6+3M[view] [source] [discussion] 2023-01-24 15:59:49
>>Firmwa+nG
So why not just run Linux in a VM? According to your description, the hardware isn't working correctly natively when running the OS on bare metal, and that's always been the reason people say against using a VM. They want the native performance, but in your case, native sux.
◧◩◪
45. josefx+bM[view] [source] [discussion] 2023-01-24 16:00:03
>>ThatMe+E5
Are you running a distro provided build or one downloaded from mozilla?
◧◩◪◨
46. nicobu+zO[view] [source] [discussion] 2023-01-24 16:08:44
>>sbaidd+gr
Firefox has improved a lot on mac in the last two years. It's still less battery efficient than Chrome, but not by too much anymore. I've just switch for it's better tab management features (tab groups).
◧◩◪◨⬒
47. zamale+vP[view] [source] [discussion] 2023-01-24 16:11:53
>>FpUser+4b
That's completely fair. The reason that everyone is half-in on Wayland is likely because it's not yet default on Ubuntu. That, and Gnome window decorations.
◧◩◪◨
48. saiya-+xP[view] [source] [discussion] 2023-01-24 16:11:56
>>nradov+hF
... and that was enough to completely destroy competition, and get a near monopoly for many years. Clearly amoral move enough that they got slapped with quite a big anti-competition fine from EU for this.
◧◩◪◨
49. angora+ZP[view] [source] [discussion] 2023-01-24 16:13:16
>>nradov+hF
I guess we'd have to argue what "aggressive" means here, but what you describe as "all they did" can and has been found to be monopoly behavior and against the law in the US. This is known as bundling and there are a bunch of prior cases which confirm it can be considered a violation of antitrust law. The bundling concept was the basis of the antitrust lawsuits against Microsoft in the late 90s.

That said, Apple is doing something worse with Safari, in that not only are they bundling the browser, they are using their tight control over the operating system to prevent other browsers from being installed in the first place. It's slighly murkier than the MS antitrust case because the counter-argument is "but they do allow other browsers! You can see Chrome/Firefox/Brave/etc in the App Store!" and then you have to get into a technical discussion of the difference between a browser application and a browser engine.

Sigh.

replies(2): >>nradov+b91 >>charci+qa1
◧◩◪◨
50. gls2ro+eR[view] [source] [discussion] 2023-01-24 16:17:19
>>kibwen+0C
You might be right - I did not check the numbers.

My idea was primarily based on my experience is something like this:

I know (meaning I know what they use) around 15-20 devs on MacOS.

Almost all of them have FF installed. Some may open it occasionally but just as an alternative to open in private mode or check some weird behavior to see if it is cross-browser or cache related.

- personal usage: except maybe 2, all the others are using Safari (most of them) and Chrome few

- professional usage: except for the same 2, here I think Chrome is more used and Safari less

Thus in these developers' case, I don't think they will recommend FF to their friends or relatives even if FF is installed on their machine as it is not their daily driver.

I am in the same category regarding usage: I forced myself multiple times to use FF. Still try to do that couple of times per year.

But fallback to Safari because the battery lasts so much longer and because it is integrated with the MacOS keychain.

One might think that with M1, people might afford to lose a bit of battery but it is the reverse. Seeing how long it lasts one barely thinks of cutting those hours short :) Could mean starting to carry again the power adapter or always looking for a table near a power socket.

Here is a browser that I installed not long ago and start to like it more and more: https://browser.kagi.com

replies(1): >>kibwen+y11
◧◩◪
51. jefftk+5S[view] [source] [discussion] 2023-01-24 16:19:37
>>rypska+ib
Firefox doesn't block statcounter or other analytics trackers by default. You'd have to go into "Settings > Enhanced Tracking Protection" and change it from "Standard" ("Balanced for protection and performance. Pages will load normally.") to "Strict" ("Stronger protection, but may cause some sites or contact a break.") While I expect Firefox users are much more likely than users of other browsers to do this, I'd also expect a large majority leave settings at the default.

You can test behavior on this tracker here: https://www.jefftk.com/test/statcounter

replies(1): >>LeifCa+0Y
◧◩◪◨⬒
52. jefftk+oS[view] [source] [discussion] 2023-01-24 16:20:43
>>onli+xw
Trackers are not blocked by default. You can verify this by visiting https://www.jefftk.com/test/statcounter in stock Firefox, and then again after setting "Enhanced Tracking Protection" to "Strict".
◧◩◪◨
53. dylan6+qS[view] [source] [discussion] 2023-01-24 16:20:45
>>kibwen+0C
I don't think anyone would ever dispute numbers claiming macOS as an also ran level of numbers. They are the kind of numbers that only impress so someone can point to them to say that the other OS isn't a monopoly.
◧◩
54. runjak+GU[view] [source] [discussion] 2023-01-24 16:28:05
>>kristi+P3
Do you mean "upset with Mozilla"? The PWA Wikipedia article claims that Safari has better PWA support than Firefox.
replies(1): >>Snitch+UW
◧◩◪
55. encryp+MW[view] [source] [discussion] 2023-01-24 16:34:25
>>ThatMe+E5
Firefox notoriously has bad performance on Linux compared to Chromium. Chromium does a pretty good job at implementing new hardware acceleration features while Firefox just got around to it like a year ago and it is still no where as performant. There is noticeable delays for me on Firefox when doing things like resizing windows in a tiling window manager as well.
◧◩◪
56. Snitch+UW[view] [source] [discussion] 2023-01-24 16:34:58
>>runjak+GU
Per [1], PWAs on webkit lacks push notifications, full-screen display, hardware acceleration, web bluetooth as major headline features needed, which Firefox on mobile appears to generally support per a 5-second glance (I didn't see web bluetooth, but the rest I did) [2].

That wikipedia page has a support table saying IOS supports PWAs as YES and Firefox as NO is odd considering Apple requires Mozilla to ship a crippled form of safari on IOS, if Firefox could ship their own true application, I suspect they would have better PWA support as a differentiator with Safari.

[1] https://thenewstack.io/owa-takes-on-apples-browser-ban-for-p...

[2] https://developer.mozilla.org/en-US/docs/Web/Progressive_web...

replies(2): >>Wevah+Ro1 >>dmitri+Ai3
◧◩◪◨
57. LeifCa+0Y[view] [source] [discussion] 2023-01-24 16:39:22
>>jefftk+5S
Thanks for the tester, on Firefox I just see:

    <html><head></head><body><img src="https://statcounter.com/" vt9kpu8nj="">
    </body></html>
but uBlock Origin with default settings blocks the image.
replies(1): >>jefftk+w01
◧◩◪◨⬒
58. jefftk+w01[view] [source] [discussion] 2023-01-24 16:48:19
>>LeifCa+0Y
Looking in the browser networking panel is probably the easiest way to see whether it actually sends a request.
replies(1): >>jmholl+eg1
◧◩◪◨⬒
59. kibwen+y11[view] [source] [discussion] 2023-01-24 16:51:55
>>gls2ro+eR
Sure, and I'm not trying to defend the performance of Firefox on MacOS (I wouldn't know). But it's easy to see why it's not necessarily Mozilla's highest priority. Hell, there are probably more Firefox users on Windows XP than Firefox users on Linux (this may sound like hyperbole, but I know for a fact it was true as of no less than five years ago).
◧◩◪
60. uoaei+Z21[view] [source] [discussion] 2023-01-24 16:56:36
>>Merely+S6
"The rich should get richer" is a common reasoning implement for the rich.
◧◩◪◨⬒
61. kitsun+t41[view] [source] [discussion] 2023-01-24 17:02:12
>>postal+DE
But at the same time, there have been several cases where Mozilla and Apple have been on the same page in terms of feelings on a particular feature/change. In one of those cases Google bulldozed through and did their own thing anyway (see WebUSB).
◧◩
62. kitsun+d61[view] [source] [discussion] 2023-01-24 17:08:25
>>kivle+ca
Power efficiency seems like an afterthought at both Google and Mozilla. I’m not sure what the reason is for Firefox, but with Chrome it like the vast majority of attention is soaked up by implementing the early draft spec of WebBananas or whatever to keep a steady stream of developer-enticing features rolling out than anything else.
◧◩◪◨⬒
63. Klonoa+n71[view] [source] [discussion] 2023-01-24 17:12:14
>>mtomwe+2a
Running on Windows/Linux/Android fundamentally does not matter. Market share does.
64. veheme+z71[view] [source] 2023-01-24 17:13:05
>>onli+(OP)
If you are in favor of Chrome on iOS, then you are in favor of a Chrome monopoly, or you don't understand how browser monopolies work. Or maybe you weren't around during the browser wars (a lot of < 30s on HN).
replies(1): >>trista+nS1
◧◩◪◨⬒
65. nradov+b91[view] [source] [discussion] 2023-01-24 17:19:41
>>angora+ZP
Describing what Microsoft did as "bundling" seems a little silly in retrospect. I mean of course a desktop OS should come with a browser. If they had just added IE as a standard feature of Windows from the start without ever selling it as a separate product then they would have had a stronger legal case. It would be absurd for antitrust regulators to prohibit software vendors from enhancing their products just for the sake of protecting competitors' revenue.
replies(1): >>angora+ZB2
◧◩◪◨⬒
66. robert+3a1[view] [source] [discussion] 2023-01-24 17:22:34
>>mtomwe+2a
Incorrect, Safari leads the pack on new feature support.
◧◩◪◨⬒
67. robert+7a1[view] [source] [discussion] 2023-01-24 17:22:41
>>postal+DE
Incorrect, Safari leads the pack on new feature support.
◧◩◪◨⬒
68. charci+qa1[view] [source] [discussion] 2023-01-24 17:23:59
>>angora+ZP
It's not bundling because a web browser is a part of a operating system. For the same reason it's not bundling if their operating system contains a scheduler or network drivers
replies(1): >>angora+BB2
◧◩◪◨⬒⬓
69. Karuna+tb1[view] [source] [discussion] 2023-01-24 17:27:51
>>iggldi+Zo
This is exactly the kind of problem that is a fork can solve when the upstream project can't or won't. I haven't used Chrome in years, but I do not notice the problem you describe in Brave.
◧◩◪◨
70. kllrno+Jb1[view] [source] [discussion] 2023-01-24 17:28:37
>>nradov+hF
It was more than that. Microsoft was giving IE special APIs that it wasn't letting others have, and was also deeply integrating IE into the broader OS (eg, embedding it into the file explorer)

Which is also what Apple is doing but then going even further and just outright banning other browser engines.

replies(1): >>Wirele+Pp3
◧◩◪◨⬒⬓
71. jmholl+eg1[view] [source] [discussion] 2023-01-24 17:46:45
>>jefftk+w01
The above poster is right. If you have uBlock Origin, it blocks it by default. I tested the following:

1. Plain install: Not blocked 2. With uBlock Origin: Blocked 3. Strict Enhanced Tracking Protection: Blocked 4. 2+3: Still blocked (unsurprisingly)

I would expect knowledgeable and concerned users (i.e. installing at least uBlock Origin) and people on systems managed by such people (e.g. family members of people in the first group who let that person manage their system) to be a higher percentage of Firefox users than other browsers.

I don't think Firefox has say a 10% share, but I do think that data derived from statcounter.com is going to underrepresent the share of Firefox users. As Google continues to make larger moves to fight ad-blocking, I expect that gap will widen.

◧◩◪◨
72. Wevah+Ro1[view] [source] [discussion] 2023-01-24 18:21:46
>>Snitch+UW
If I’ve read correctly [1], Safari on macOS 13 (released after the mentioned article) supports the standardized Web Push APIs.

[1] https://developer.apple.com/documentation/usernotifications/...

◧◩◪◨⬒
73. leland+8u1[view] [source] [discussion] 2023-01-24 18:40:47
>>postal+DE
This is a very uncharitable assessment. They drag their feet on API support but they're still a part of the interop group and actually were more conformant by the end of last year on the targeted features than Chrome: https://wpt.fyi/interop-2022

There's a case to be made that they handicap PWA features, but I don't see their team directly implementing features incorrectly.

◧◩
74. error5+3D1[view] [source] [discussion] 2023-01-24 19:12:33
>>Gorbze+vs
> Many of those who have not learned from history are so anti-Apple (or possibly subpar webdevs) that they completely ignore the lessons we've previously learned about why browser monoculture is dangerous.

I'm confused, because to me it seems that the pro-Apple folks are the ones ignoring the lessons from large corporations using their weight to force monocultures.

Firefox is the only meaningful browser that is open and won't be leveraged by its steward to promote their business interests.

replies(1): >>dmitri+1j3
◧◩
75. trista+nS1[view] [source] [discussion] 2023-01-24 20:09:31
>>veheme+z71
This is a false dichotomy. Open competition is not an endorsement for monopolies.
replies(1): >>veheme+YH5
◧◩◪◨⬒⬓
76. angora+BB2[view] [source] [discussion] 2023-01-24 23:47:29
>>charci+qa1
> a web browser is a part of a operating system

This was not at all the case in the 90s during the period of MS antitrust action.

> For the same reason it's not bundling if their operating system contains a scheduler or network drivers

There is a robust market (even today) for web browsers, and the makers of browsers make millions of dollars in revenue from their products. Therefore, I disagree, and I believe the bundling concept could still apply today to browsers. Network drivers and schedulers are not at all the same, because there isn't much of an independent market for them.

◧◩◪◨⬒⬓
77. angora+ZB2[view] [source] [discussion] 2023-01-24 23:49:50
>>nradov+b91
> I mean of course a desktop OS should come with a browser.

This was not that obvious in the 1990s.

> It would be absurd for antitrust regulators to prohibit software vendors from enhancing their products just for the sake of protecting competitors' revenue.

This is absolutely a situation where a bundling case could apply, if a large incumbent uses their monopoly power in one product area to enter another and unfairly compete. IANAL but I don't believe whether or not the product was available separately or not would factor much into such a case.

◧◩
78. musica+3E2[view] [source] [discussion] 2023-01-25 00:05:07
>>kristi+P3
> Apple for (clearly intentionally) lacking support for PWA features

It's in Google's interest to replace native iOS apps with web apps.

It's in Apple's interest to replace web apps with native iOS apps.

Native apps also tend to be more power efficient and to present a platform-native look and feel.

I don't see any incentive for Apple to support PWAs (or Google's vision for web apps) ever.

◧◩◪◨⬒⬓⬔
79. capabl+JE2[view] [source] [discussion] 2023-01-25 00:09:57
>>FpUser+jH
So you don't run browsers on Linux, I don't see what you have a problem with then? The particular issue you're complaining about doesn't seem to affect you at all.
replies(1): >>FpUser+0c4
◧◩◪◨
80. dmitri+Ai3[view] [source] [discussion] 2023-01-25 06:10:25
>>Snitch+UW
> web bluetooth as major headline features needed

"web bluetooth" and many other hardware APIs are Chrome-only non-standards that OWA pretends are standards and core features for PWAs.

◧◩◪◨⬒
81. dmitri+Si3[view] [source] [discussion] 2023-01-25 06:12:29
>>postal+DE
> Safari seems to rather build their own web then obey standards that both firefox and chrome are following

wat. Firefox and Safari are more closely aligned on standards support than Chrome which pushes its own non-standards aggressively

◧◩◪
82. dmitri+1j3[view] [source] [discussion] 2023-01-25 06:14:40
>>error5+3D1
Please read "Breaking the Web Forward" https://www.quirksmode.org/blog/archives/2021/08/breaking_th...

--- sart quote ---

Back fifteen years ago IE held back the web because web developers had to cater to its outdated technology stack. “Best viewed with IE” and all that. But do you ever see a “Best viewed with Safari” notice? No, you don’t. Another browser takes that special place in web developers’ hearts and minds.

--- end quote ---

replies(1): >>error5+rQ4
◧◩◪◨⬒
83. Wirele+Pp3[view] [source] [discussion] 2023-01-25 07:26:38
>>kllrno+Jb1
Eh, we could still write a browser that interfaced with those special APIs, albeit in a hidden fashion.

And even without them, we could write a browser and distribute to people so they could install it.

That cannot be said about iOS.

◧◩◪◨⬒⬓⬔⧯
84. FpUser+0c4[view] [source] [discussion] 2023-01-25 14:10:33
>>capabl+JE2
Where did you see me complaining about the issue? I just stated my opinion that it should be in general task of the software to figure out the environment it is running under and adjust accordingly.
◧◩◪◨
85. error5+rQ4[view] [source] [discussion] 2023-01-25 17:06:11
>>dmitri+1j3
Oh you're absolutely right about Chrome, I'm just not sure why you mention 'anti-Apple', because Apple's leverage is being used in many of the same ways, just much more aggressively than 'best viewed in IE', instead it's 'App Store/WebKit/<choose your monoculture> or pound sand'.
replies(1): >>dmitri+h15
◧◩◪◨⬒
86. dmitri+h15[view] [source] [discussion] 2023-01-25 17:49:12
>>error5+rQ4
> I'm just not sure why you mention 'anti-Apple'

Said nothing about "anti-Apple". I'm just agreeing with the poster above saying that people being vehemently anti-Apple actually haven't learned anything from history. At all.

> Apple's leverage is being used in many of the same ways, just much more aggressively than 'best viewed in IE'

Of course this is bullshit. Again. There's probably not a single site out there that is "best viewed in Safari". And there are numerous sites that are "best viewed in Chrome". Including, especially, the ones that Google themselves (#1 search, #1 mail, #1 video hosting, #1 web ad business in the world) creates.

And to quote again:

--- start quote ---

Regardless of where you feel the web should be on this spectrum between Google and Apple, there is a fundamental difference between the two.

We have the tools and procedures to manage Safari’s disinterest. They’re essentially the same as the ones we deployed against Microsoft back in the day — though a fundamental difference is that Microsoft was willing to talk while Apple remains its old haughty self, and its “devrels” aren’t actually allowed to do devrelly things such as managing relations with web developers. (Don’t blame them, by the way. If something would ever change they’re going to be our most valuable internal allies — just as the IE team was back in the day.)

On the other hand, we have no process for countering Google’s reverse embrace, extend, and extinguish strategy, since a section of web devs will be enthusiastic about whatever the newest API is. Also, Google devrels talk. And talk. And talk. And provide gigs of data that are hard to make sense of. And refer to their proprietary algorithms that “clearly” show X is in the best interest of the web — and don’t ask questions! And make everything so fucking complicated that we eventually give up and give in.

--- end quote ---

Google releases 400 new APIs a year with little to no oversight and with complete disregard of any objections or concerns from the other browser vendors: https://web-confluence.appspot.com/#!/confluence

The things that you think Safari is lacking in are largely Chrome-only non-standards.

replies(1): >>error5+KM5
◧◩◪
87. veheme+YH5[view] [source] [discussion] 2023-01-25 21:11:02
>>trista+nS1
First, can you explain how you came to interpret my particular statement as a universal one? It doesn't seem like a good faith reading. If you doubt that a Chrome monopoly results from Chrome on iOS, that's an argument you can make, but it doesn't look terribly plausible.

Second, your use of "open competition" is doing a lot of heavy lifting here, suggesting that browser market share is determined by ordinary market forces (it's not) or that Apple isn't competing openly with Google already. Why would allowing the competitor's browser on your hardware be considered "open competition?" Again, it's not clear.

◧◩◪◨⬒⬓
88. error5+KM5[view] [source] [discussion] 2023-01-25 21:38:02
>>dmitri+h15
My comments in this thread are almost exclusively about the odd assertion in my parent that somehow 'anti-Apple' folks are the ones who have ignored history's lessons about monocultures. I'm not presenting this as an Apple <-> Google dichotomy; in fact nearly the opposite, both companies are fighting for monocultures that they control, just in slightly different domains. Apple wants to control the client platform, Google wants to control the web. Neither is good for users. It's very odd to me that someone would frame this discussion as 'anti-Apple' people missing the point. I won't speak for others, but I, as an anti-Apple person, am absolutely vehemently against this return to 'best viewed in IE', but I am also opposed to operating system developers and hardware vendors dictating what users are able to do with their own shit and insisting on putting their grubby paws on every dollar that passes through.

That is why I use Firefox, as the only remaining browser that hasn't shown a long-term pattern of curtailing user freedoms or rights when it suits them. I don't see Safari as a solution here; Apple is not pushing for an open web because it is righteous, they are pushing for a platform they control and to hurt their competitor. They are not to be trusted either. If they can, they will absolutely leverage that control against the user as they have shown time and time again that they are more than willing to do.

> Of course this is bullshit. Again. There's probably not a single site out there that is "best viewed in Safari". And there are numerous sites that are "best viewed in Chrome". Including, especially, the ones that Google themselves (#1 search, #1 mail, #1 video hosting, #1 web ad business in the world) creates.

When I say 'Apple', I mean 'Apple', not 'Safari'. Apple are the ones with a platform that will not run unblessed code. Apple are the ones that don't let developers or users choose how software is distributed. Apple are the ones that tell you which APIs you can and cannot use, and what your app can and cannot do. Apple are the ones that tell you what browser engine you can run, which is much stronger than a website saying 'yeah we tested this against IE, but go nuts', instead it is Apple saying 'if you want a browser engine, you can take Webkit or pound sand'. This is Apple's modus operandi, writ large. At least with Google's level of control you can still do what whatever you want with the website that runs in Chrome.

[go to top]