Live data from Hacker News

Firefox 36.0 released

mozilla.org

31–40 of 256 posts

Re: Firefox 36.0 released

#31
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.

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...)

Speaking as a different user, one who looks at the task manager a decent amount, I really appreciate not having 49 different Firefox processes. This is definitely an issue of personal preference as it's been debated back and forth here a good amount, so no side is really "right" regarding single process v. multi process, but I'm firmly in the former camp.

Re: Firefox 36.0 released

#32

Yay! 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.…

[deleted]

Re: Firefox 36.0 released

#33

While 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…

Your complaint seems to be that they haven't shipped a huge project which a bunch of people are working on and adding a backwards-compatibility hack for people who use older network hardware which generates incorrect self-signed SSL certs but also choose not to install valid certificates on this device.

I mean, it would be great for a few people if they added the ability to ignore this check but it's not a surprise that it's a lower priority compared to implementing HTML5/ES6 features which will provide a better web experience for millions of people.

Re: Firefox 36.0 released

#34
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.

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...)

I'd rather they make the code more robust to make crashes unlikely enough that they can actually debug and fix them when they occur, rather than going multi-process as a band aid to make recovery easier on a user

That said, it is easy to recover from simply by re-opening FF and you're right back where you were and I haven't had a total browser crash in a long time. I do experience lock up issues though

Re: Firefox 36.0 released

#35
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.

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...)

There are other users you probably don't represent.

Re: Firefox 36.0 released

#36

Earlier quoted context omitted.

Don't forget about FireBug which is pretty awesome.

I heard it was an unmaintanable mess, that's why Mozilla added in-house devtools. I liked FireBug UX more, but I like that Firefox has metalevel coding/debugging capabilities out of the box (the smalltalk fan speaking).

It was, it also was slow as hell. Now it's much better. I don't see any issues, but then again I run pretty fast pc.

Re: Firefox 36.0 released

#37
post #21

> No longer accept insecure RC4 ciphers whenever possible What do they mean with "whenever possible"? If there is a downgrade attack ongoing, will it be possible to avoid RC4?

Here are more details, with links to the discussions on specific issues. https://developer.mozilla.org/en-US/Firefox/Releases/36#Secu...

Re: Firefox 36.0 released

#39

Earlier quoted context omitted.

For the curious, the duplicate SSL cert issue is in regards to some buggy routers and wireless printers with broken firmware. They send out invalid SSL certificates. Firefox doesn't have a way to provide an exception to allow access when security is compromised in this way but the user doesn't care and wants to access it anyway. The only reason tabs generally misbehave is if Flash crashes. Firefox separates Flash out…

No, the certs are otherwise valid, but the problem is that once Firefox has seen a cert for a given address, if another address presents an identical cert, the second address cannot be browsed to without shutting down the browser and deleting the entire cert store. Other offenders off the top of my head: BMC interface on Intel boards, HP iLO for blade management, F5 load balancers. Yeah, they shouldn't be doing that,…

I find it curious that the people complaining about this don't instead install valid certificates. That was routine for us even a decade ago because otherwise you're literally training your admin staff to ignore errors and enter sensitive passwords every time a security warning pops up.

That's never good and it feels dangerously close to professional negligence when it's a password which gives privileged access to a server.

EDIT: just to be clear, I don't think this is “these people are crazy” so much as “what reason is good enough to justify leaving yourself exposed like this?” Even the cheap devices I bought in the early 2000s allowed you to install SSL certs and installing something real was a routine part of the first-time install.

Re: Firefox 36.0 released

#40

Earlier 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...)

Speaking as a different user, one who looks at the task manager a decent amount, I really appreciate not having 49 different Firefox processes. This is definitely an issue of personal preference as it's been debated back and forth here a good amount, so no side is really "right" regarding single process v. multi process, but I'm firmly in the former camp.

Firefox multiprocess, by default, has just one process for all the tab content and one for the "chrome". You can increase the number of processes used for tab content manually in about:config.
Post reply on HN