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

Firefox 36.0 released

mozilla.org

Post reply on HN
Print view View original

91–100 of 256 posts

Re: Firefox 36.0 released

#91

Post by sp332 »

bobcostas55 wrote: post #59
Ded7xSEoPKYNsDd wrote: post #28

Earlier quoted context omitted.

Session restore in Firefox has been lazy for a long time now (the tab only loads when you activate it). It doesn't take longer than loading a single page. How often do tabs crash for you? That's the real issue if you ask me. I'm on Nightly (with Electrolysis!) and the last crash was over 2 months ago.

>It doesn't take longer than loading a single page. Yeah, because it only loads a single page. It doesn't actually restore anything. Sometimes the pages it restores aren't even the live version but a cached one, I have no idea when or why it does that. It's absolutely infuriating.

Right-click any tab -> Reload All Tabs. If you want a permanent solution, go to about:config and double-click browser.sessionstore.restore_on_demand.

Re: Firefox 36.0 released

#92

Post by dblohm7 »

tshtf wrote: post #16
sp332 wrote: post #10

Earlier quoted context omitted.

Adding multi-process to a large project that was not designed for multi-process is an astronomical amount of work. And Firefox's approach has advantages over Chrome's, so they're not simply playing catch-up.

Chrome's first public release, which included multiprocess tabs, was on December 11, 2008. There has been more than enough time for Mozilla to catch up.

They didn't have an addon ecosystem to contend with back then.

Re: Firefox 36.0 released

#95

Post by dblohm7 »

jherdman wrote: post #61

I'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

#96

Post by dblohm7 »

izolate wrote: post #70
jherdman wrote: post #61

I'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…

One minor grievance I have with the Firefox console is the input line is all the way at the bottom. I quite like Chrome's approach of starting at the top. Firefox has a few of these irritating UX quirks that I just can't get over. Having to restart after installing an extension is another. Every time I see the request, I can't help lose a bit of respect for it.

File a bug if you want to request devtools improvements.

Re: Firefox 36.0 released

#97

Post by dblohm7 »

dochtman wrote: post #55
drzaiusapelord wrote: post #43

Earlier quoted context omitted.

I'm not sure why you're being downvoted so much. I assume the usual FOSS fanboyism that rules HN. I used Chrome, IE11, and Firefox all day. FF is the only one that locks up and crashes on me. Its so rare in the other browsers I'm shocked when it happens in FF. I run almost no extensions and I think my copy at work has zero extensions and I don't even have flash installed, so the idea that it must be a plugin problem…

This sounds very different from my experience. Have you ever looked at about:crashes and checked into any bugs hanging off your crash signatures? (And if not, please file bugs!) If you make a list of your crashes available, I'd be happy to take a look and see if I can dig out some explanation for your problems, or make sure the appropriate bugs are on file with Mozilla. I know for a fact that Mozilla leadership does…

THIS. Developers on HN with problems have the requisite skills to be able to file good bugs.

Re: Firefox 36.0 released

#98

Post by pslam »

higherpurpose wrote: post #11
mcdoug wrote: post #3

Wow this is a big release! HTTP 2.0, phasing out 1024 certs, sync, will-change. BTW, is there already support for 4096 certs? Or is that coming later?

Why 4096-bit RSA certs when you can have ECC certs?

There are installations which don't support ECC, usually due to hardware limitations, but do support RSA-4k. Often this cert is the trust anchor for various other uses than just SSL, so the result is you end up using RSA-4k instead of ECC.

There's also folks who don't entirely trust ECC because it's "too new". To be fair, RSA isn't broken, and 4k is sufficiently big to be safe even with a partial break.

Re: Firefox 36.0 released

#100

Post by drzaiusapelord »

dblohm7 wrote: post #97
dochtman wrote: post #55

Earlier quoted context omitted.

This sounds very different from my experience. Have you ever looked at about:crashes and checked into any bugs hanging off your crash signatures? (And if not, please file bugs!) If you make a list of your crashes available, I'd be happy to take a look and see if I can dig out some explanation for your problems, or make sure the appropriate bugs are on file with Mozilla. I know for a fact that Mozilla leadership does…

THIS. Developers on HN with problems have the requisite skills to be able to file good bugs.

I've been filing bugs for years yet the QA of the product is still at unaccepatable levels. FF's constant passing of the buck is bothersome. When they can't blame extensions they blame people for not participating. Yet somehow Chrome/Chromium exists just fine without me writing big reports for it, same for Safari, IE, etc.

FF just has poor QA. That's a problem and all the excuse making actually hurts the product as FF leadership isn't seeing enough complaints apparantly, when an army of nerds are refusing to acknowledged these problems.

Post reply on HN