Live data from Hacker News

No to Chrome

notochrome.org

151–160 of 319 posts

Re: No to Chrome

#151
post #81
post #9

I have been using Firefox for several years now. Energy management is still an unsolved problem on MacOS (Firefox 71 on 10.14.6). They have been making improvements in the last several releases, but "Avg Energy Impact" remains around 40 for me (when browsing web pages, higher when streaming video). I also noticed how different colors are between Chrome and Firefox. That becomes more obvious in the dark mode. https://…

The comments from noel@chromium.org in this bug report are scary. "We're not doing as the spec tells us to, BUT that probably gives us performance gains, most users don't care about it anyway, I prefer it that way, webdevs should fix it, we should fix the JPEG standard instead (!?)..." Why so much resistance?

> most users don't care about it anyway

Our designer was pissed off when we discovered this bug, which explained why Chrome was the only program that displayed RGB values differently from all the others (not just browsers). She'd been careful about standardizing and tweaking colors we already used to work better for people with colorblindness, much of which was thrown out the window on Chrome. Not to mention issues matching the PNGs and SVGs she created for the site.

Quick edit:

> Why so much resistance?

Comment 34:

> Chromium developers have previously stated this won't be supported for reasons mentioned in this old post.

> https://www.webkit.org/blog/73/color-spaces/

From that link (posted in 2006):

> The big hurdle that we ran into, though, was with the drawing we did not control, namely the Flash plug-in. The problem is that designers specify colors in Flash and colors in CSS in the Web page, and they expect those colors to match. Because Flash’s drawing isn’t correcting to sRGB, if we did it in Safari, there would be color mismatches all over the place. These mismatches look far worse than if we just don’t correct at all.

Isn't Flash gone from Chrom(ium) now?

Re: No to Chrome

#152

Earlier quoted context omitted.

But Safari still supports extensions, surely? I’m using it with extensions, there are not stories I can see about them removing support, and their Développement pages are still up.

Safari does still support extensions, but they operate differently now.

True, but the extension ecosystem is poor now.

1. Extensions in the app store are not easily searchable. They aren't indexed/sorted on the store properly, and many only show up on Google.

2. Many of the good extensions are no longer available, e.g., UBO and KeePass, Vimium (there is a Vim extension, but it's a poor replacement so far).

3. The store promotes junkware and throwaway extensions.

Re: No to Chrome

#153
Does anyone know the Firefox dev tools equivalent of Chrome dev tools "JavaScript contexts" drop down menu? I'm not sure how to describe it, but here are two screenshots from a tutorial where I saw it:

1. With mouse hovering over the drop down menu showing the displayed tool tip

https://imgur.com/a/16lCRWg

2. With clicked on drop down menu showing the "javascript contexts"

https://imgur.com/a/SPZuvWr

Re: No to Chrome

#154

Even if you have no issue with Google, this is still a good idea to encourage competition. Honestly, Chrome is not as good as it used to be anyway. For me, Google Maps and Waze are the hardest things to kick. And YouTube...

I use https://maps.openrouteservice.org/ and find it to be perfectly adequate.

Pretty good, but it doesn't do public transport.

Re: No to Chrome

#155
post #116

Earlier quoted context omitted.

> The problem isn't Chrome or Google per se, it's technology. We should be pressuring the big guns to conform to our needs, not opting out... How do you propose to do that without boycotting? I'm all for regulating overly large corporations, but until that happens I can also vote with my feet.

Organize politically, at the state level, at the federal level, whatever you deem appropriate and achievable. Push for privacy laws, push for laws around data ownership. Develop a theory of "what should people own" and "what kind of behaviors should be prohibited by companies" and "what kind of disclosures should be required." Develop a message and start hammering your reps, and get like-minded techies and community…

Yes, I had the same thoughts, then I figured out that vast number of techies are earning from the fishy practices we should protest against. And barely anyone is prepared to protest against something that pays for his even if he knows it is wrong. We had a few people leaving google and facebook but vast majority stays or those companies would go out of job by only management left. And not only for tech, this is the same on all levels of life.

Just check the threads here when GDPR was introduced, oh all the rage.

Don't blame the companies, politics,...

They are the best what society can offer.

If world is filled with corrupt, egoistic, narcissistic, greedy (etc.) people, the companies that are made by exactly the same people, are also corrupt, greedy (,...).

Same goes for politics. And everything else.

The society needs to change. But. There is barely anyone left to push the change. There is barely anyone who understands that there is a need for change.

Re: No to Chrome

#156
post #53

Less Google, more internet. Simple as that

If by "internet" you mean the more traditional thought of internet with all of its decentralized goodness (and services and such), then YES 1000 times!!

Re: No to Chrome

#157
post #16
post #15

Earlier quoted context omitted.

I was using Safari up until they have yanked support for extensions. The web is unusable, outright hostile place without a proper script blocker. I can tolerate a lot of things, but browsing the web without uBlockOrigin isn't one of them.

Then go with Brave. They stripped out the Google bits, and they won't remove support for the current uBlock Origin ad blocker.

Why Brave rather than the Epic Privacy Browser?

(They are both based on Chromium....)

Re: No to Chrome

#158
post #132

Earlier quoted context omitted.

You've skipped a rather large period of time in which people would travel, and would bring a map with them or buy one when they got there. You think road trips only got to be a thing after Mapquest?

It was obviously an exaggeration but maps are just an iterative improvement until we landed (for now) GPS enabled devices, in the future we'll maybe have it embedded in our glasses, eyes or brain. I didn't say that we could only start traveling or doing road trips once we invented smartphones.

GPS-enabled devices are the first such improvement to have a novel downside: you can now be tracked, whether you want to be or not.

Re: No to Chrome

#159

Does anyone know the Firefox dev tools equivalent of Chrome dev tools "JavaScript contexts" drop down menu? I'm not sure how to describe it, but here are two screenshots from a tutorial where I saw it: 1. With mouse hovering over the drop down menu showing the displayed tool tip https://imgur.com/a/16lCRWg 2. With clicked on drop down menu showing the "javascript contexts" https://imgur.com/a/SPZuvWr

Oh, by "js contexts" do they mean "all the javascripts related to the page?" If so, then I guess this file tree-like explorer of js is the Firefox equivalent?

https://imgur.com/a/YvA9Hdw

Re: No to Chrome

#160
post #137
post #76

Interesting, I just moved back to Firefox after many years of using Chrome. I have to admit, it has gotten a lot faster recently, Firefox sync is working very well, and the Firefox Android app is a pleasure to use (being able to install uBlock origin is a huge plus). Anything else I missed on Chrome was easily solved by an addon, or a small tweak on userChrome.css (customizing the browser interface by overriding its…

I can’t solve highlighting search results in the scroll bar, and apparently I search a surprising amount and am absolutely crippled without scroll bar highlighting, so I’ll stick to Chrome until I can’t (e.g. when content blocking is crippled).

>> ... highlighting search results in the scroll bar...

This. I find any browser that doesn't do that to be unusable. The alternative, in long documents or source code, is to blindly hit NEXT and visit all locations where a search term is found rather than scrolling quickly to see the different context regions.

I tried a plug-in or two but they were not nearly as functional as the native Chrome experience.

Post reply on HN