Live data from Hacker News

No to Chrome

notochrome.org

201–210 of 319 posts

Re: No to Chrome

#201

Earlier quoted context omitted.

Note how all of these Brave promotion comments are from new accounts...

I had no intention to promote or advertise brave, nor am i affiliated or working for the brave browser. if that's what you imply.

But do you hodl BAT?

Re: No to Chrome

#202
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).

TIL. So funny, I've been using Chrome since the beginning, and I've never noticed this feature, and I search all the time. I am now switching between Firefox and Chrome among various laptops, and I am impressed with Firefox. At some point, Firefox may become my dominant browser.

Re: No to Chrome

#203
post #170

Earlier quoted context omitted.

Glad I’m not insane, or not the only one insane. Whenever I read one of these highly-voted “I switched to Firefox and nothing’s degraded” post I wonder if I’m the only one searching on web pages, or if I’m the only one whose productivity is massively boosted by knowing where search results are located and how they are clustered at a glance. But then, modern code editors do tend to have this feature, so apparently it…

> modern code editors do tend to have this feature, so apparently it is important to a non-negligible audience Sorry, but as far as the modern browsers are concerned, we coders are a negligible market to cater for. The number of non-coder browser-users is orders magnitude higher than the number of coders.

Not saying coders are a non-negligible audience (although I’d say coders are a non-negligible segment of Firefox user base). My assumption is that the percentage of coders who value scroll bar highlighting is comparable to the percentage of those among all web users who read and search web pages of nontrivial length, since there’s hardly anything about this feature that’s specifically beneficial to coding.

This and the fact that I heard all the “switched to Firefox and nothing’s degraded” comments from coders, and upvoted by coders.

Re: No to Chrome

#204
post #122

Does anyone use the Brave browser? I started a few days ago and it's a pretty interesting idea.

Search the page and you'll find several mentions of Brave. What I want to know is why someone would pick Brave instead of the Epic Privacy Browser... ... though personally, I think it's far better to support Firefox as it's now the only viable alternative browser that isn't based on Chrome. Chrome is now so dominant that people can just ignore open web standards and develop for Chrome instead. This is a Bad Thing.

I'll check out Epic, but I think Brave has a neat solution for supporting websites with BATs.

Re: No to Chrome

#205

Earlier quoted context omitted.

In terms of browsers, I have moved back to Firefox from Google for my personal/professional browsing, but I have a product that is heavily reliant on Puppeteer and CDP. There are moves towards interoperability in Firefox, but that's my current blocker.

It's a shame WebDriver hasn't been improved. Instead we get an entirely separate, nonstandard effort from the vendor with a supermajority.

(WebDriver standard contributor and member of the team working on this in Gecko)

There is a plan to update the WebDriver standard to encompass the automation features that are currently only available via devtools protocols. There's agreement it should be possible to open up a bidirectional channel to the browser from within devtools and use it for things like listening to events, streaming logs, etc. However as so often happens reality dictates that implementing something compatible with CDP is needed today in order to interop with the range of existing tooling that's either CDP-only (e.g. Puppeteer) or WebDriver-with-CDP-extensions (e.g. SauceLabs, various WebDriver clients).

In the long term we hope that we end up with a "WebDriver 2.0" that will satisfy all the common use cases in a standard way. That bidirectional protocol will probably end up looking a lot like CDP just to ease the migration for existing implementations, but the details depend on work that hasn't yet been done.

Re: No to Chrome

#206
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…

it's literally the same engine as chrome. the only reason i use chrome is for the dev tools.

Have you tried Firefox's dev tools in Firefox 71? As far as I can tell they're way better than Chrome's.

Re: No to Chrome

#207

Earlier quoted context omitted.

it's literally the same engine as chrome. the only reason i use chrome is for the dev tools.

FF just got web socket inspectors so I really don't know what chrome dev tools has now. Everything about ff dev tools is better. Especially looking at css layouts.

This has finally allowed me to switch. I’ve been trying to since quantum came out two years ago, but this was always a deal breaker.

Firefox is generally still a little buggier and less performance in my experience, but not so much that I want to switch back. Hopefully they can stay relevant.

Re: No to Chrome

#208
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?

> I prefer it that way, webdevs should fix it, we should fix the JPEG standard instead

Wow. Just wow. I have rarely seen so much ignorance. And this exactly why Chrome is cancer for the whole internet. I mean, seriously, why should the web developers fix something that is standardized just to make it work in Chrome? And fixing the JPEG standard...?

Re: No to Chrome

#209
That claims about Youtube. Especially "YouTube has contributed to a growth of the flat earth conspiracies at the expense of scientific fact."

Do you understand how algorithm or statistics works?

They are giving people what they want. Freedom. People is watching that videos and made them more popular. They are free to share their thoughts.

Even google can't predict all the negativeness and prevent them with computer systems. Expecting being a god from google is unfair.

I think this is hate for google more than arguments against google.

I dislike chrome and using Firefox for a long time. But i don't think this is objective and completely true.

Re: No to Chrome

#210
post #71

Chrome/ium is a wonderful web development environment. Can't see myself moving away from it any time soon.

Firefox DevTools member here. If you have tried them recently, I'd love your feedback on what's blocking you.

No op, but for me I use Chrome's "Replay XHR" constantly. Literally 100s of times/day. So I appreciate that it's simple as right-click->open menu->left-click "Replay XHR". AND that it takes me right back to where I was before: namely either the "Response" "tab" (not sure what to call that menu tab/option) or "Preview" "tab". AND that the "Preview" "tab" automatically detects and renders the JSON returned from my server.

FF requires several clicks to re-run XHR. And doesn't return me to where I was before. And doesn't render my JSON.

Thanks for listening.

Post reply on HN