Live data from Hacker News

We Need Chrome No More

redalemeden.com

21–30 of 536 posts

Re: We Need Chrome No More

#21
post #4

> developers are increasingly shunning other browsers in their testing and bug-fixing routines. If it works as intended on Chrome, it’s ready to ship. That's me. Sorry, but I just can't be bothered to support every browser's quirks. I check Firefox every once in a while, but really, I don't mind losing a few users if it means significantly less maintenance and testing for me. It's like complaining that developers are…

The more things change, the more they stay the same.

Linux, macOS and Windows aren't variations of the same OS APIs.

Re: We Need Chrome No More

#22
post #7

I enjoyed this post, but I take issue with the idea that Chrome was initially adopted, or served, "to break the Web free from corporate greed." Chrome's appeal was primarily technical. Each tab got its own process and could crash without taking down the entire browser. No one else had this at the time, and it was a big deal because Flash was still widespread so sites were even less stable than they are today. Luckily…

In my experience I can't stream video on firefox without the video freezing within the first 5 minutes, and it feels clunky even with non video webpages. I really hate google the company, and I'd love to stop using their software, but so far I have yet to see a browser that even comes close to chrome.

What OS, hardware and video platform(s)? I haven't had any issues with Desktop Firefox on Windows 10 on any of my Core i7 machines, when watching YouTube/Vimeo. Even my old dual-core budget Inspiron 3137 laptop works for YouTube and Firefox as well as Pandora/Firefox/bluetooth audio blasting.

(It does like to consume RAM as if it was running SQL Server though.)

Re: We Need Chrome No More

#23
post #7

I enjoyed this post, but I take issue with the idea that Chrome was initially adopted, or served, "to break the Web free from corporate greed." Chrome's appeal was primarily technical. Each tab got its own process and could crash without taking down the entire browser. No one else had this at the time, and it was a big deal because Flash was still widespread so sites were even less stable than they are today. Luckily…

> Each tab got its own process and could crash without taking down the entire browser. No one else had this at the time

IE8 Beta 1 shipped March 5, 2008; Chrome's beta release wasn't till September. OK, admittedly, Chrome's stable release happened before IE8's, but MS was working on much the same thing.

Re: We Need Chrome No More

#24
post #7

I enjoyed this post, but I take issue with the idea that Chrome was initially adopted, or served, "to break the Web free from corporate greed." Chrome's appeal was primarily technical. Each tab got its own process and could crash without taking down the entire browser. No one else had this at the time, and it was a big deal because Flash was still widespread so sites were even less stable than they are today. Luckily…

> Chrome's appeal was primarily technical Among the tech crowd, probably. For the remaining 99.99% of users, absolutely not. Chrome's appeal came from the pervasive advertisement campaigns, from the bundling strategy with other pieces of software, for the pre-installation on new computers or from the ads on Google SEarch homepage.

I switched to chrome before I became technically literate, because it seemed a lot faster and less prone to breaking. I couldn't describe why, but the effect was felt.

Now, I still struggle to move to firefox as I'm on a retina MBP, where firefox riles up my cpu and drains my battery.

Re: We Need Chrome No More

#25
post #7

I enjoyed this post, but I take issue with the idea that Chrome was initially adopted, or served, "to break the Web free from corporate greed." Chrome's appeal was primarily technical. Each tab got its own process and could crash without taking down the entire browser. No one else had this at the time, and it was a big deal because Flash was still widespread so sites were even less stable than they are today. Luckily…

> Chrome's appeal was primarily technical. Each tab got its own process and could crash without taking down the entire browser.

Curious, I remember speed being the primary reason. Google invented V8 (the javascript engine), with some pretty decent optimizations and a well-working JIT on i386/amd64 platforms. At the time when chromium came out, it handled some JS-heavy applications very nicely that Firefox struggled with.

There seems to be a bloat cycle with many products, browsers being one of them. They start off lean, gain features over time, and then they are or feel so heavy that a lean new competitor can feel like a fresh breeze.

Remember when Firefox was the fresh breeze, compared to the Netscape suite? I remember Chrome being perceived the same way when it came out.

Re: We Need Chrome No More

#26
Extensions. I am now locked into Chrome because several services I use require Chrome extensions that aren't available elsewhere. The idea that Chrome can be unseated, or isn't needed, is unrealistic for the many users who rely on Chrome-exclusive extensions.

Re: We Need Chrome No More

#27
post #13
post #4

> developers are increasingly shunning other browsers in their testing and bug-fixing routines. If it works as intended on Chrome, it’s ready to ship. That's me. Sorry, but I just can't be bothered to support every browser's quirks. I check Firefox every once in a while, but really, I don't mind losing a few users if it means significantly less maintenance and testing for me. It's like complaining that developers are…

Developing against Chrome is exactly "support every browser's quirks" instead of developing against the actual standards (usually Firefox has the truest implementation of which).

But as a web developer I don't necessarily care about standards. I want the page to work for as many users as possible. For the longest time this meant to support IE's way of doing things, now it means to support Chrome (unless you target Enterprise users).

Even if you develop for Chrome, Firefox and Edge you'll just end up building workarounds for all 3, not adhering strictly to the standard.

Re: We Need Chrome No More

#28
There is an important difference between Google and Microsoft. Google is using their market dominance to push their opinions on the open standards bodies; Microsoft used their market dominance to ignore standards bodies completely.

Re: We Need Chrome No More

#29
Where we are now, it's not hard to look at Chrome in a negative light, for all the reasons the article states. However, I still remember where I was when I first saw the Chrome "speed test" ad, and thought "wow, this is what a browser should be! https://www.adsoftheworld.com/media/film/google_chrome_speed...

Re: We Need Chrome No More

#30
post #13
post #4

> developers are increasingly shunning other browsers in their testing and bug-fixing routines. If it works as intended on Chrome, it’s ready to ship. That's me. Sorry, but I just can't be bothered to support every browser's quirks. I check Firefox every once in a while, but really, I don't mind losing a few users if it means significantly less maintenance and testing for me. It's like complaining that developers are…

Developing against Chrome is exactly "support every browser's quirks" instead of developing against the actual standards (usually Firefox has the truest implementation of which).

Chrome is the new IE?
Post reply on HN