Comment by babby | Hacker News Reader

Comment by babby | Hacker News Reader

Parent Full thread

I use both browsers regularly, but Firefox out of preference. It amazes me at how under performing chrome has become over the years. Font rendering, for one. The fact that they STILL don't have DirectWrite font rendering on Windows, something that has been with IE and FF since FF 3.6, amazes me.

Good luck trying to get a webfont to render the same (or look any good) in Chrome as it does in IE and FF on Winderps. The sheer fact that it isn't IE for once...

The font thing, while somewhat recent in usage, should have been in Chrome ages ago. Not going to bother getting into Chromes other more critical flaws as I feel like these threads devolve into this kind of shit too easily.

Just sucks that Chrome has gone from this cool browser that actually is progressive, to some kind of Ad-friendly extension of Google that just qualifies as "better than IE!".

Methinks you should jump on FF, it's better, and not because it may not support some arbitrary HTMl5 spec that we wont see for half a decade.

It seems many Chrome users have last used FF 3.6 and still compare Chrome to that. Meanwhile Chrome has gotten slow and annoying. The old "boiling frog" anecdote comes to mind.

Yep. I remember Chrome was blasting fast when I switched to it when it appeared. I switched back to FF few months ago and I like it better, especially on Android.

I went back to firefox and could not be happier.

Indeed, with firebug for debuging and firefox sync, ever single feature I liked in Chrome is done as well or better in FF. Add the bonus that it performs faster and is leaner on memory, and I dropped Chrome some time ago.

Does Firebug pretty print minified JavaScript now?

Yes

If there is I couldn't find the option

The thing about Chrome is that while the font rendering is horrible the dev tools are super awesome. At work I end up using FF for reading text and Chrome for inspecting/debugging.

What's your opinion of Firefox's new developer tools?

Firebug is much better.

- Tools like YSlow and PageSpeed require Firebug.

- You can't disable the browser cache from FF devtools, which really sucks when you are trying to debug a broken redirect.

- When inspecting an element in FF devtools, :before and :after CSS properties will not be shown. I wasted many hours debugging a CSS refactor because of this (imagine going up the DOM, comparing computed CSS properties until you reach the root). Both Firebug and Chrome devtools will show :before and :after properties.

I think Firebug and the Chrome devtools are comparable in quality.

> Chrome devtools will show :before and :after properties.

And on that, I was plesently surprised to see Chrome will now display :before and :after psuedo elements in the DOM structure

> When inspecting an element in FF devtools, :before and :after CSS properties will not be shown.

It was fixed recently. https://hacks.mozilla.org/2013/09/new-features-in-the-firefo...

Can you even debug a web worker with Firebug? How about SourceMap support? The times when I've had to switch to FF devtools have been pretty painful. The profiling and tracing tools in chrome also seem lightyears better.

The profiler is nice, a lot better than Chrome IMO.

The responsive design view is very handy. It switches the size of the view port without changing the size of the whole window. I still use firebug most of the time, but there are some issues with firebug you have to be careful of. See this post for an example http://perfectionkills.com/understanding-delete/#firebug_con...

One of my main reasons for using FF is firebug. That said, chrome's dev tools are wonderful and I'll often use both in tandem.

I would switch back to FireFox if I could figure out how to remove the titlebar so that my tabs properly lined up with the top of my screen. (Running under Linux Mint Cinnamon).

Try this

https://code.google.com/p/mactype/

Reply on news.ycombinator.com