I noticed that, too. And I'm on 21.0
Except for those who prefer to use Firefox.There's only one solution to the browser question: Chrome.
I've been very happy with Firefox lately (past year and a half) since they sorted out memory leaks and have zero issues with it whatsoever.
Previous to that I was pulling my hair out using it with it's memory usage/leak issues on a machine (6 years old at the time) with 1 gig of memory and trying to use photoshop at the time. Much much better nowadays though.
I hve yet to make a return to FF since i had to ditch it back then in favor of Chrome.. Personally glad FF was such a POS otherwise id never have bothered to download chrome.
Been causing lots of caching issues lately.
I think it's mostly what you are used to. I used to not be able to do without Firebug. But ever since Google hired the lead Firebug developer to work on Chrome a couple years ago, the Chrome debugger has gotten tremendously better (and now it's much better than Firebug in my opinion). But really just comes down to what you are familiar with I think.If there was a full version of firebug for chrome I would switch in a heartbeat. I find Chrome significantly faster and the only reason I don't use it because of it's code inspector, I just can't get on with it whatsoever.
I think it's mostly what you are used to. I used to not be able to do without Firebug. But ever since Google hired the lead Firebug developer to work on Chrome a couple years ago, the Chrome debugger has gotten tremendously better (and now it's much better than Firebug in my opinion). But really just comes down to what you are familiar with I think.
http://news.softpedia.com/news/Lead-Firebug-Developer-Joins-Google-Chrome-Team-212278.shtml
I've never needed to add any special code for Firefox.It's kind of sad what's happened to Firefox in the last few years (it used to be my browser of choice)... now it's the new IE... always needing to build custom CSS and things for Firefox bugs and just features/CSS that other browsers have but it lacks.
Been causing lots of caching issues lately.
I noticed that, too. And I'm on 21.0
Chrome is a little bit of the same. Final version seems to eat more resources. And I never understood as to why. It's why I usually tell people to use Chrome beta.
Browsers are like religions. People like what they like.
By a significant amount, or... ?
I run both builds side-by-side, on the same machine, at work, often for weeks on end, and I'd say resource usage has been pretty much the same across both in my experience. So, that's interesting.
I do, but Opera in the past had page rendering issues. It started to remind me of Internet Explorer. Things would load fine in Firefox, Chrome, and Safari, but Chrome would go all crazy.It seems nobody use Opera...
Its one of those odd little things that you kind of wonder, why, but ya never exactly figure it out and simply come to just accept it.
I think its more noticeable in Firefox though. The Beta usually is more stable and doesn't have the issues that the final version seems to "mysteriously" adapts. And Aurora feels more like a beta than an alpha.
Chrome does the same thing. They'll push out the final version and people will complain about something (there are a few things on XenForo about general Chrome issue) and the first thing I tell them is switch to the Beta. And usually, the problem suddenly is gone.
We use essential cookies to make this site work, and optional cookies to enhance your experience.