Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

mastodon.social

Post reply on HN
Print view View original

401–410 of 602 posts

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

#401

Post by bee_rider »

simiones wrote: post #292
INGSOCIALITE wrote: post #150

Earlier quoted context omitted.

> What difference do you see between a browser and an OS? A browser is an OS. They perform the same role. A context to run whatever 3rd party software. This is where everything has gone screwy. A browser should only be rendering and displaying html files. Browsers should be minuscule in size, and /definitely/ not run any 3rd party software.

The web was invented in 1989, became a public project in 1991, and JavaScript support for it appeared in 1995, Java Applets the same year, with Flash and ActiveX following in 1996. So it was a static document model for ~6 years, and an app platform for ~27 years.

PDFs and work documents also were infected with scripting languages in the 90’s. It was just a weird time.

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

#402

Post by 8K832d7tNmiQ »

omgmajk wrote: post #209

* The "Manifest v3" sabotage of content blocking extensions: https://archive.is/i2vGD * The attempted sabotage of #JPEGXL: https://archive.is/2ihEV * #WebEnvironmentIntegrity a.k.a. #DRM for whole websites would hurt the web, #opensource browsers and OSes: https://archive.is/S912x

Need to mention WebUSB[1] too since it's only implemented and forced on Chromium.

[1]: https://caniuse.com/webusb

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

#404

Post by webstrand »

andrewla wrote: post #374
sph wrote: 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…

> It's 2023, Safari and Firefox have been very good for a while. This has not been my experience. Every once in a while I try to make the switch (to Firefox because I'm not generally a mac user, but I use safari on iOS and I'm basically resigned to its limitations) Slow rendering is for sure a problem. Buggy rendering is very common -- maybe the site, or maybe the browser, who knows, but anecdotally I've had a lot of…

I do a bunch of CSS work, and I've found more bugs in Chrome's rendering than in Firefox's, Lots of half-pixel errors. What kind of rendering issues are you seeing in Firefox?

If you do a lot of web development, I strongly recommend getting familiar with Firefox's containers. You can set up SOCKS proxies for each individual container so you can easily pretend your dev server is running on the production server's domain without disabling your own access to the production servers. It's so much nicer than working with multiple proxies in Chrome.

That said, you might enjoy ungoogled-chromium if you're annoyed by google-integration. I use it for testing (because cross-browser testing is still a must). Brave also exists and is open-source, to break up market share.

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

#405

Post by horsawlarway »

mrtksn wrote: post #332
spoiler wrote: post #246

Earlier quoted context omitted.

> Remember the "Safari is the new IE" narrative? Just because Safari doesn't support some API doesn't make it IE It wasn't because they had poor feature adoption. It was because they'd tend to adopt features in a way that's incompatible with other browsers (of the top of my head, handling of localStorage in private browsing). It was a bit of a "fuck you" to devs since you often had to do browser detection for Safari…

Apple probably have similar motives to MS when it comes to crippling the browser and enforcing its own rendering engine in iOS and that is to protects its app market. However, Apple did not attempt to divide the web then use its dominant position to make all the content only compatible with their stuff. With the IE situation, you couldn't just download Firefox and live happy thereafter because every website was made…

> However, Apple did not attempt to divide the web then use its dominant position to make all the content only compatible with their stuff.

Excuse me? We are talking about "App store" Apple here, right? The Apple that prevents any 3rd party browsers on their platform so devs have to support safari? The Apple that refused to support progressive web apps to push devs into their store?

The Apple which literally won't let users install software they don't approve of, Apple? That Apple?

That's the company you're picking as "didn't attempt to divide the web"? Ooof.

You've been drinking so much Kool-aid your tongue is purple.

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

#406

Post by dclowd9901 »

sph wrote: 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…

Dev experience in chrome is a lot better. But for personal browsing I use safari and mainly only because of how it uses keychain.

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

#407

Post by carimura »

hliyan wrote: post #207
sph wrote: 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…

For a Mac M1 user who wants a lightweight browser, what would you recommend: 1. Safari (with this, I have trouble with some websites, particularly Google ones) 2. Firefox (good, but has been a memory hog in the past) 3. Brave (like that it's Chromium, but I worry about the odd features like crypto) 4. Edge (I just downloaded it. leaning toward this choice)

I use Brave with Brave Rewards disabled and I almost forget anything Crypto related exists.

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

#408

Post by Vinnl »

foobarbecue wrote: post #280
sph wrote: 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…

I'm afraid to switch because: - Chrome dev tools is consistently amazing and I use several extensions on it - I use google password manager which is also amazing and it works seamlessly on all my android devices, even filling passwords into android apps (although most people don't seem to know it exists) Sooner or later, I will get around to switching back to FF, but it's daunting. I used FF before Chrome came out.

Just a note that Firefox's password manager can also fill passwords into Android apps.

(I also think that its devtools are really good too, but I imagine habit is a large part of that. Of course, it's also an option to open Chrome only when you need the devtools.)

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

#409

Post by mrtksn »

horsawlarway wrote: post #405
mrtksn wrote: post #332

Earlier quoted context omitted.

Apple probably have similar motives to MS when it comes to crippling the browser and enforcing its own rendering engine in iOS and that is to protects its app market. However, Apple did not attempt to divide the web then use its dominant position to make all the content only compatible with their stuff. With the IE situation, you couldn't just download Firefox and live happy thereafter because every website was made…

> However, Apple did not attempt to divide the web then use its dominant position to make all the content only compatible with their stuff. Excuse me? We are talking about "App store" Apple here, right? The Apple that prevents any 3rd party browsers on their platform so devs have to support safari? The Apple that refused to support progressive web apps to push devs into their store? The Apple which literally won't le…

We are talking about browsers actually. The grunge that web developers have against App Store is baseless because its what saved the open web so far.

Check out the linked article, the moment Chrome have its way into iOS, the web will die because Google will have IE level dominance. The web as we know it goes away, the browser becomes an AppStore where everything is optimised for data collection and ad serve. We already have an AppStore, let's keep having a WWW.

And about the anger towards the AppStore? Well, you should be able to overcome it by drinking some herbal tea.

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

#410

Post by kesildur »

sph wrote: 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…

Firefox dropped support for PWAs. :(
Post reply on HN