Live data from Hacker News

A list of recent hostile moves by Google's Chrome team

mastodon.social

191–200 of 602 posts

Re: A list of recent hostile moves by Google's Chrome team

#191
post #181
post #175

Earlier quoted context omitted.

i’ve been a happy safari user (desktop and mobile) for years now.

What adblock do you use with Safari? Last time I've tried, I couldn't find one and returned back to Firefox.

I just checked mine and its using this:

https://apps.apple.com/us/app/adblock-pro-safari-ad-blocker/...

I have zero issues with this setup.

Re: A list of recent hostile moves by Google's Chrome team

#192

Earlier quoted context omitted.

Firefox on Linux is just fine, no idea what you are talking about. It is fine on Android, too (uBlock Origin!).

Have you compared it to other browsers? What distro do you use? I've benchmarked performance on Arch, Fedora, Debian and Ubuntu and found that Firefox was 2-3x slower than most chrome forks.

Slower may be true, but is it slow to you? Are you actively loading hundreds of web pages and need Firefox to be that much faster for them?

Maybe it's just because I live far away from host servers that aren't from local companies, but real world latency between your machine and the web server is IMO more important than the browser loading a page 200ms faster than another.

Re: A list of recent hostile moves by Google's Chrome team

#193
post #183

Earlier quoted context omitted.

I have a serious question about Brave. I would be glad to use it, but I am a bit scared of the fat that it is linked to a crypto (I didn't dive in the tokenomics, but maybe the team is driven by the money ? or other shady things ?), and also the fact that I go ads for this browser. Getting an ad for the browser make me question: what are their incentives ? Why would they invest money to attract people ? What is their…

I have the wallet/bat token stuff turned off. Its not even turned on when you install Brave. The main reason I moved to Brave is Firefox's bizarre updating model on Ubuntu which causes it to randomly shutdown all the time. Plus on Android, brave just blocks a ton off ads, that firefox doesn't without extensions and fiddling about.

Is it Firefox's bizarre updating model or Ubuntu's bizarre updating model? On my Arch, Firefox updates work fine.

Re: A list of recent hostile moves by Google's Chrome team

#194

Earlier quoted context omitted.

Many of my work tools require a browser extension that's only compatible with Chrome. The publishers don't plan to support Firefox or any other browser. I can do without these tools (not an easy task) but not my coworkers.

You can install adons from the Chrome store in Brave.

I assume most tech-savy people will want to stay far away from a browser that uses cryptonomics to confuse people into feeling better about blocking ads.

Re: A list of recent hostile moves by Google's Chrome team

#195
post #120
post #57

Remember the "Safari is the new IE" narrative? Just because Safari doesn't support some API doesn't make it IE, IE wasn't an inferior browser at the beginning either. What made IE the IE everyone hates was its departure from standards(?) and enforcing its own vision of the web thanks to its enormous market share. On IE's case, MS probably stagnated it to prevent competition against its desktop Apps business and on Go…

Standards were never the real problem; they were always a joke. I don't think Netscape/Mozilla ever once changed their behaviour to match a standard; rather the standards "committee" was in their pocket for some reason, and would rubber-stamp any proposal from their side no matter how stupid, from the box model onwards. Every "standard" from 4.0 onwards was a step backwards; eventually they approved enough pointless…

There is some truth in this. IE had a box model a bit like TeX's. Divs stacked inline and spans sat side by side so you easily make very sophisticated layouts. Navigator's box model was dumb as a rock in comparison. Divs started a new vertical context like they do now. So Navigator's model was standardised as the lowest common denominator. It would have been pretty much impossible at the time to retrofit IE's model into Navigator, and it was years before inline blocks were supported in Firefox. It's not so surprising that Microsoft didn't downgrade their browser to meet the standard.

Re: A list of recent hostile moves by Google's Chrome team

#196

Earlier quoted context omitted.

Many of my work tools require a browser extension that's only compatible with Chrome. The publishers don't plan to support Firefox or any other browser. I can do without these tools (not an easy task) but not my coworkers.

You can install adons from the Chrome store in Brave.

I think the point isn’t necessarily to not use chrome but to use something not based on chromium in general, which brave is, e.g. Firefox or Safari.

Re: A list of recent hostile moves by Google's Chrome team

#198
post #142

What is the excuse of all people reading this thread in agreement and still using Chrome? As I mentioned elsewhere, this is preaching to the choir. A choir of Chrome users. Google wouldn't be so dominant if tech people like us would stop making lazy excuses to continue its hegemony. In Dante's Divina Commedia , there is a circle of hell for those too lazy to take a stance [1]. If it were written today, it would inclu…

Chrome renders websites as the site esigners designed. It's a game theory dilemma.

Re: A list of recent hostile moves by Google's Chrome team

#199
post #74
post #57

Remember the "Safari is the new IE" narrative? Just because Safari doesn't support some API doesn't make it IE, IE wasn't an inferior browser at the beginning either. What made IE the IE everyone hates was its departure from standards(?) and enforcing its own vision of the web thanks to its enormous market share. On IE's case, MS probably stagnated it to prevent competition against its desktop Apps business and on Go…

Safari caused me by far the most issues, back when I was doing frontend in ~2017/2018, in terms of how it complied with web standards (I wasn't as fussed at the standards it didn't support - at least I knew!) and rendered the web application I was working on across desktop, iPad and iPhone. I spent more time chasing Safari bugs and rendering idiosyncrasies than I did dealing with IE11, frankly.

Nothing compares to IE6. That was a hellscape.

Re: A list of recent hostile moves by Google's Chrome team

#200
post #177

Earlier quoted context omitted.

There's nothing weird about the obsession. It's the most technically impresive format so far.

avif? webp?

https://avif.io/blog/comparisons/avif-vs-webp/

> AVIF has an image resolution limit of 65536 x 65536 pixels.

but from https://tonisagrista.com/blog/2023/jpegxl-vs-avif/

> Max image size is limited to 4K (3840x2160) in AVIF, which is a deal breaker to me. You can tile images, but seams are visible at the edges,

> WebP also has a hard limit to an image's frame size, with its maximum dimension being 16,383 x 16,383

> WebP supports a max bit depth of 8-bit

> AVIF flexes a max bit depth of 10

Jpeg XL has progressive rendering support https://opensource.googleblog.com/2021/09/using-saliency-in-...

AVIF spec doesn't (although it might gain it: https://bugs.chromium.org/p/chromium/issues/detail?id=122171...)

JPEG-XL manages to be more efficient than other current formats: https://cloudinary.com/blog/jpeg-xl-how-it-started-how-its-g...

All of that while being a good all-around image format (rather than a specialized one like webp and avif): same format for web, photos, raw photos, etc. To me, this makes it the most noteworthy image format now.

Post reply on HN