Live data from Hacker News

Firefox 36.0 released

mozilla.org

121–130 of 256 posts

Re: Firefox 36.0 released

#121
post #70

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.

> Firefox has a few of these irritating UX quirks that I just can't get over.

Another one is not being able to use shift-home or shift-end to select to the beginning or end of a css property.

Re: Firefox 36.0 released

#122
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?

Anyone know of a brief list of workarounds/schemes/optimizations that probably won't be needed (or will be less needed) with http2?

(or just add to this list)

- css sprites

- monolith js/css-files

- rotating through 'alias'-subdomains for resources

- trimming cookies / cookie-less domains (for request-headers)

Re: Firefox 36.0 released

#123
post #50

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.

I have a crash probably every day. Usual culprit is Flash.

Counter-anecdote: I use Firefox all day every day and usually have 100s of tabs open. I haven't had a legitimate full-browser crash in years. I've had a hang that resulted in me having to kill the process probably 3 times in the last year. I usually don't enable Flash, but when I do, it usually doesn't crash, and when it does, it just takes out all instances of Flash currently running; doesn't bring down the whole browser. I'm on Linux.

If you're getting a lot of Flash-induced crashing, you may want to check into alternate implementations of Flash, like Gnash, Lightspark, or even Mozilla's Shumway.

Re: Firefox 36.0 released

#124
post #91

Earlier quoted context omitted.

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

No need to use about:config, it's on the first page of options.

Re: Firefox 36.0 released

#125
post #120

Earlier quoted context omitted.

As I understand it, add-ons are updated more slowly than their Chrome counterparts because Mozilla actually reviews the code of each add-on offered from their store to attempt to validate it's not doing anything naughty. Google and Apple make these types of promises, but really they approve things after a cursory glance and then respond to any user complaints that may come in.

On the other hand I read that the review process is quite slow (as in painfully slow)

Yeah, this is the tradeoff. It takes a long time to audit code. Supposedly Mozilla is doing this every time an add-on update is sent for review. Google and Apple just pretend like they do, and I guess Mozilla didn't get the memo that you're supposed to pretend.

Re: Firefox 36.0 released

#126

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

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…

> If MS did this in IE people on HN would be losing their shit

If they changed people that had set it to google, sure.

But changing the default? That's not something to be mad about.

Re: Firefox 36.0 released

#127

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…

As I understand it, add-ons are updated more slowly than their Chrome counterparts because Mozilla actually reviews the code of each add-on offered from their store to attempt to validate it's not doing anything naughty. Google and Apple make these types of promises, but really they approve things after a cursory glance and then respond to any user complaints that may come in.

Yes, FF/Mozilla trying to be perfect delay lots of things. They should ship fast, fix later (and not be perfectionists).

Re: Firefox 36.0 released

#128
post #91

Earlier quoted context omitted.

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.

No need to use about:config, it's on the first page of options.

Oh! You know I was staring at that... Yeah, just click "Options" and then uncheck "Don't load tabs until selected". Thanks!

Re: Firefox 36.0 released

#129

Earlier quoted context omitted.

Which is one of the main reasons I still use Firefox.

Please explain this line of reasoning. As is it reads as "I still use Firefox because I like that 1 tab can bring down the the whole browser"

Chrome is utterly unsuited to the use case of leaving hundreds of tabs open, which happens often to me, as I only bother updating/cleaning my bookmarks a couple of times a year. There's three main issues with Chrome:

1) Nothing I've found that works nearly as well as Tree Style Tab.

2) Chrome always reloads all tabs when the browser starts up. Firefox, at least with Session Manager, will only load old tabs when I activate them.

3) Chrome takes up way more memory. That's partly due to #2, but partly inherent in the multi-process model.

The Chrome UI also gets weird under load. With Firefox, it's easy to tell when it's laggy. With Chrome, the UI seems asynchronous, but there's no consideration for actions taking a long time, so you can get the annoying feeling of clicking with nothing obvious happening.

Re: Firefox 36.0 released

#130

Meanwhile, in firefox 39a (current nightly), a reader view (readability/printfriendly) http://imgur.com/DONqb30

I see font rendering in linux is still pretty horrible.

Font rendering is as configured. See https://wiki.archlinux.org/index.php/Font_configuration
Post reply on HN