Firefox 36.0 released
mozilla.org
Firefox 36.0 released
1–10 of 256 posts
Re: Firefox 36.0 released
#2Your web, the way you like it.
Re: Firefox 36.0 released
#3Wow 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?
Re: Firefox 36.0 released
#4Semi-OT: is anyone on HN using a "alternative" Browser such as Midori or Vivaldi on a daily basis? I love what Midori is doing but it still crashes on me to often.
Re: Firefox 36.0 released
#5While 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], making the browser completely unsuited to enterprise administration uses. One misbehaving tab can still kill your entire session. I understand that they're working on this with the electrolysis project, but end of 2015 goal?[2] I don't mean to be overly snarky here, but congratulations on getting to where Chrome/ium was back in 2008.
I seriously question how the priorities are being decided at Mozilla. These are basic usability things that were solved in other browsers a long time ago.
Re: Firefox 36.0 released
#6Thank you for the best browser out there!
Re: Firefox 36.0 released
#7Yay! 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.
JS debugger feels worse and clunky compared to Chrome.
Element inspector feels like duplo to chromes lego (does that make sense?)
I opened firefox yesterday and found a new speach bubble icon asking me to connect to O2 for something. WTF?! WTactualF is that all about?
/rant
Re: Firefox 36.0 released
#8Yay! 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).
Re: Firefox 36.0 released
#9Wow 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.
Re: Firefox 36.0 released
#10While 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.