Live data from Hacker News

No to Chrome

notochrome.org

141–150 of 319 posts

Re: No to Chrome

#141

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...

Apple Maps is now quite usable if you're on iOS...although it's no Waze.

Apple Maps meh. It doesn't work across devices. I look maps on my browser all the time. I need maps to appear everywhere and be sharable with the 80% of the planet not using iOS

Re: No to Chrome

#142

Earlier quoted context omitted.

It's better to provide facts and references rather than just making opposing statements.

The burden of proof is for the original statement ("it's literally the same engine"), not the counter.

Yes but a blunt counterstatement doesnt make for good reading. Far better is to provide some substantiation so everyone can learn as your more highly voted siblings did!

Re: No to Chrome

#143
post #134
post #94

Earlier quoted context omitted.

Firefox uses the Gecko engine, while Chrome uses Blink. The engines don't even have a shared ancestor.

“Originally” if I recall correctly, Chrome was a fork of firefox right? That is a long time ago though!

Nope. It was a fork of WebKit which was a fork of KHTML, the engine powering Konqueror. KHTML was developed by the KDE team.

Edit: It was widely speculated that Apple would use gecko for Safari and a shock when they announced they would use the relatively little known KHTML engine. The decision was based on KHTML having much cleaner code. I haven't looked at the Mozilla code in many years, but it was pretty gnarly back then. Lots of old cruft from the Netscape days. In comparison, KHTML was beautiful.

Re: No to Chrome

#144
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.

I'm loving pihole https://pi-hole.net/

Pi Hole is a good first layer, but good sites occasionally have bad shit on them, so you can't rely entirely on host-based blocking.

Re: No to Chrome

#145
post #28

Earlier quoted context omitted.

They scrape top results and show it directly in a box (think wikipedia, imdb, lyric engines etc.) thus discouraging users from actually clicking the link. Personally, I think it’s nice to have the content instantly available and not having to go to a website for it but I can see how for content producers this means wrapping their websites and making money out of their content.

Wasn't that something their search copied from ddg?

No. Google's OneBox, Ask’s Smart Answers, Microsoft’s Instant Answers, and Yahoo Shortcuts all existed at least two years before DDG was even founded in 2008.

Also, DDG's "Instant Answers are open source and are maintained on GitHub, where anyone can build or work on them". https://en.wikipedia.org/wiki/DuckDuckGo

It's not the same sort of massive web-scraping click-stealing operation as Google's OneBox.

Re: No to Chrome

#146

Is it better to push people to firefox and safari or include Opera and Edge as well so we don't get another defacto standard?

You should definitely not be pushing anyone to Safari. Apple's monopoly on browser engines on iOS gives them veto power on all web standards since iOS uses have no alternate browser engines (like Firefox)

Re: No to Chrome

#148

Earlier quoted context omitted.

OpenStreetMap had solid data, but my periodic attempts at finding a good app haven't been successful.

https://maps.me/ is a pretty mainstream option.

With removed ads and binaries https://f-droid.org/en/packages/com.github.axet.maps/

Re: No to Chrome

#149
post #139
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…

Has firefox solved its long standing issue with the rendering of radio buttons?

Maybe. If you refer to a more specific issue, it's easier to give a definitive answer though.

Re: No to Chrome

#150
post #71

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

I used to think the same, but now do all web dev in Firefox. For my purposes it has parity with chrome, and works just as well. Also means if it works in Firefox it will most likely work in chrome. The opposite was not always true.

> Also means if it works in Firefox it will most likely work in chrome.

Can’t relate at all. In my limited frontend experience, I’ve run into a lot of rendering deferences between WebKit and Blink, and even more between Gecko and Blink. Sometimes the differences are subtle yet break pixel perfection; sometimes the whole layout is broken.

Post reply on HN