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

We Need Chrome No More

redalemeden.com

Post reply on HN
Print view View original

251–260 of 536 posts

Re: We Need Chrome No More

#251

Post by j0nathanB »

VBprogrammer wrote: post #188
perlgeek wrote: post #25

Earlier quoted context omitted.

> 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 w…

I'm surprised there aren't more people on here who moved to chome for the dev tools. That is what moved me over there. Firebug was great in it's day but at some point Chrome's dev tools just became too much better to make staying on Firefox possible.

I thought Firefox’s Developer Edition had decent dev tools.

Re: We Need Chrome No More

#252

Post by twblalock »

TheRealPomax wrote: post #106

The problem with these articles is that the recommendation always ends up just preaching to the choir: people who already switched away from Chrome nod in appreciation, but people who haven't switched literally get nothing out of these posts to convince them to switch to what is basically the same application made by a different company, with completely different conventions on where everything is, without any concre…

You hit the nail on the head: the problem with overturning the status quo is that you can't offer an alternative that is just as good -- it needs to be better.

Re: We Need Chrome No More

#253

Post by greglindahl »

brazzledazzle wrote: post #183
behringer wrote: post #150

Earlier quoted context omitted.

I've used firefox and never bothered with chrome as a daily driver. The speed issue is entirely marketing driven. Nobody cares about a few tenths of a second of load times until the ads were shoving stats down our throats that chrome was so much faster Firefox is and has always been perfectly adequate, except maybe for a few html5 canvas type apps.

It wasn’t entirely market driven. Chrome was collectively faster, smoother and tab crashes were isolated which was critical back then. My dad was firmly middle aged when it came out and was very attached to Firefox. After a few debates we did some very unscientific desktop-to-page render comparisons as well as loading some pretty js heavy sites and chrome beat Firefox handily. He still took a while to come around and…

Sounds like your Dad would not have switched without your advocacy.

Re: We Need Chrome No More

#254

Post by pier25 »

bobajeff wrote: post #191
jarjoura wrote: post #129

This is such a fairytale retelling of history. Firefox was well on the way to crushing IE. It was the whole reason Microsoft re-kick started IE development again. Firefox was the dominant browser in 2008. Safari was the browser pushing ahead on performance and being lightweight except in JavaScript. So Google took WebKit and added their own JS engine to it so that Gmail and their office suite could compete with Micro…

Firefox was never the dominant browser. Neither was it on its way to crushing IE. You my friend are recalling a fairytale.

Indeed: http://gs.statcounter.com/browser-market-share#monthly-20090...

Re: We Need Chrome No More

#255

Post by om2 »

perlgeek wrote: post #25
mapgrep wrote: 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 w…

v8 was initially 32-bit x86 only. And it wasn’t coded in a CPU independent way or word size independent way at all. Adding a new CPU amounted to basically rewriting the whole JIT. Chrome took a long time to go 64-bit for this reason.

Re: We Need Chrome No More

#256

Post by pjmlp »

lucb1e wrote: post #232
bobajeff wrote: post #89

Earlier quoted context omitted.

Don't see Google pausing Chrome's development for 4 years like Internet Explorer.

I honestly don't remember what the last time was Chrome introduced some cool new feature in Chrome. Maybe the PDF reader?

PWA, WebComponents, File Access, Worklets and Houdini and everything else in HTML5/CSS3 still missing from ChromeOS are all being pushed by Chrome.

Re: We Need Chrome No More

#257

Post by tschellenbach »

Chrome is just a better browser. Also, Google already has all my information, so who better to trust with my browsing history?

Firefox has >10% market share, it's not like anybody can ignore 10% of users. So this article to me sounds like pure content marketing for Firefox.

Re: We Need Chrome No More

#258

Post by zapzupnz »

samirm wrote: post #157
TheRealPomax wrote: post #106

The problem with these articles is that the recommendation always ends up just preaching to the choir: people who already switched away from Chrome nod in appreciation, but people who haven't switched literally get nothing out of these posts to convince them to switch to what is basically the same application made by a different company, with completely different conventions on where everything is, without any concre…

>"with completely different conventions on where everything is" ...what?

GP is talking about how other web browsers have different conventions for where different web browsers place standard UI elements. Tabs on top, tabs beneath the addresss bar, separated search bars, different icons and terminology for the same concept, different items in the "share" pop ups, different placement of global menus, different customisability of the basic user interface layout, etc.

These are things to which we technically minded can easily adapt, but for the less technically literate it's bewildering, confusing, and possibly enough to make them angry.

Re: We Need Chrome No More

#259

Post by Aser »

VBprogrammer wrote: post #188
perlgeek wrote: post #25

Earlier quoted context omitted.

> 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 w…

I'm surprised there aren't more people on here who moved to chome for the dev tools. That is what moved me over there. Firebug was great in it's day but at some point Chrome's dev tools just became too much better to make staying on Firefox possible.

I'm not a professional web developer, but in the experience I've had building a couple of JS heavy sites, I've actually found the Edge developer tools to be the best. If there's one thing microsoft knows how to do well, it's build developer tools.

Re: We Need Chrome No More

#260

Post by rhlsthrm »

dak1 wrote: post #34

Other browsers need to catch up to Chrome with their development tools. I'd be happy to use Safari or Firefox for development, but... - I can't disable CORS in Firefox (yes, sometimes you have to disable CORS rather than modify the Allow-Origin header response, for example if you need to test against a production backend) (and, no, CORS Everywhere is not a sufficient solution). - I can't inspect WebSocket frames in a…

I switched recently to using Safari for all my browsing except when I need DevTools, then I just fire up a Chrome window. Only having one Chrome tab open instead of dozens seems to help performance and battery life on my MacBook as well.
Post reply on HN