Years after switching to Chrome, I've given FF 35 another chance as my main browser in the past week. The major drive was Chrome's poor handling of dozens of open tabs, which was slowing down my Macbook to a crawl (8GB Core i7 2012 13" Retina on Yosemite) way too often. "The great suspender" extension helped somewhat, but it felt like a lot of manual work for something I believe the browser should handle much more sm…
Firefox 36.0 released
251–256 of 256 posts
Re: Firefox 36.0 released
#252I'm presently in the middle of an experiment to use Firefox (and its Developer Edition) as my primary browser when performing my duties as a web developer. So far... It's been kind of rocky. Daily usage of the browser isn't that bad, but the developer tools are lacking compared to Chrome. A good example is the Network tab. In Chrome, I need only have the developer tools open to capture information about requests. In…
How about filing some bugs for your concerns?
Re: Firefox 36.0 released
#253Earlier quoted context omitted.
> There are installations which don't support ECC, usually due to hardware limitations Isn't RSA much more computationally expensive than ECC? What hardware can do RSA but not ECC? /me sits down to be schooled
Since I can't edit: EDIT: Unless you're referring to embedded systems that can't be updated?
Actually, not just embedded systems. There's HSMs (hardware security modules) which also can't be updated to support new functions. Often this is because the underlying primitives have been implemented in fixed-function hardware to prevent timing, power and even RF analysis.
Re: Firefox 36.0 released
#254Earlier quoted context omitted.
You should install Firebug. It's better than the integrated dev tools in almost all areas. About writing extensions we had this on HN in September 2014 https://news.ycombinator.com/item?id=8285744
You should install Firebug. It's better than the integrated dev tools in almost all areas. Really? I un installed Firebug not so long ago, having concluded that it offered little added value any more, while measurably, repeatably, and dramatically reducing Firefox's performance. Has either or both of these things changed in the last few months?
[1] https://blog.getfirebug.com/2014/03/26/firebug-2-0-alpha-1/ [2] https://blog.getfirebug.com/2014/06/10/firebug-2-0/
Re: Firefox 36.0 released
#255Earlier quoted context omitted.
That doesn't matter. The pixel output of subpixel rendering only works on monitors with the pixel layout it's intended for.
whoa, that is something i never thought about before.
Re: Firefox 36.0 released
#256Recently switched back to Firefox. Their search engine selection option is so easy and excellent. On Chrome, non-technical people won't be able to change default search engine. Thanks Mozilla.
I strongly prefer the previous search bar UI, and thankfully it's still available through a setting. about:config -> browser.search.showOneOffButtons = false.
Aside from that, what is the benefit of the new design supposed to be? It looks like it's designed for touch, but Firefox on touch-based platforms has a completely different UI anyway. And even if someone were to use the desktop version of Firefox with touch input, the targets look a bit small. So I don't understand the point of making the UI worse for keyboard and mouse input.