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?
Firefox 36.0 released
11–20 of 256 posts
Re: Firefox 36.0 released
#12While it's nice to see the progress being made here, it's a little bit.. what's the word here? Strange? Disheartening? Annoying? Infuriating? ..to see long-standing issues being ignored or back-burnered in the march to add all the new features. Duplicate SSL certs still cause sites to be unviewable without stupid and security-breaking workarounds that are not necessary in other browsers, for nearly 7 years now[1], ma…
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.
Understood, but I'm speaking from the viewpoint of a user, here. It's a massive annoyance for a crashed tab to annihilate the other 49. (And the session restore being activated is generally grounds for a smoke break, because your system will be tied up for a while...)
Re: Firefox 36.0 released
#13Wow 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?
Yeah, the full HTTP/2 support was a pleasant surprise! Wonder if Google's (and other prominent ones) web properties have switched over to HTTP/2 from SPDY yet.
According to http://spdycheck.org/#google.com google.com supports "h2-14" and "h2-15" which I'm guessing are drafts of HTTP/2?
Re: Firefox 36.0 released
#14Yay! Time for another firefox rant. I love the idea of firefox and I used to love it a lot. But not now. I keep trying it and always go back to chrome. It crashes. A lot. Like, at least once a day I have to ctrl+alt+del and restart it on my laptop. It freezes and the window stops responding, it doesn't even paint. In the inspector, the DOM breadcrumb area scrolls and moves around. It's like the blink tag, only worse.…
It's just that chrome devtools are really, really well made in many dimensions. But keep in mind that Mozilla has been catching up a lot (impressive knowing the budget difference) both in devtools and under the hood (memory usage).
Don't forget about FireBug which is pretty awesome.
Re: Firefox 36.0 released
#15Earlier 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.
Understood, but I'm speaking from the viewpoint of a user, here. It's a massive annoyance for a crashed tab to annihilate the other 49. (And the session restore being activated is generally grounds for a smoke break, because your system will be tied up for a while...)
But the issue isn't ignored or back-burnered.
Re: Firefox 36.0 released
#16While it's nice to see the progress being made here, it's a little bit.. what's the word here? Strange? Disheartening? Annoying? Infuriating? ..to see long-standing issues being ignored or back-burnered in the march to add all the new features. Duplicate SSL certs still cause sites to be unviewable without stupid and security-breaking workarounds that are not necessary in other browsers, for nearly 7 years now[1], ma…
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.
Re: Firefox 36.0 released
#17Wow 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?
Yeah, the full HTTP/2 support was a pleasant surprise! Wonder if Google's (and other prominent ones) web properties have switched over to HTTP/2 from SPDY yet.
Using FirefoxDevEdition with SPDY indicator shows me Google, Youtube and Twitter over HTTP/2.
Re: Firefox 36.0 released
#18Wow 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?
I for one welcome our EdDSA-ECDHE-AES-GCM overlords.
(I know we're not there yet :P)
Re: Firefox 36.0 released
#19Earlier quoted context omitted.
Understood, but I'm speaking from the viewpoint of a user, here. It's a massive annoyance for a crashed tab to annihilate the other 49. (And the session restore being activated is generally grounds for a smoke break, because your system will be tied up for a while...)
But the issue isn't ignored or back-burnered.
That was more directed at the F-ING SSL issue, but still, end of 2015 to have a feature that's considered standard nowadays and introduced 7 years ago?
How much of the work that went into deprecating certs and removing obscure command line flags and setting up HTTP/2 (which isn't even really used by anyone yet) could have went into electrolysis?
Re: Firefox 36.0 released
#20Meanwhile, in firefox 39a (current nightly), a reader view (readability/printfriendly)