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

111–120 of 256 posts

Re: Firefox 36.0 released

#111

Post by laumars »

shmerl wrote: post #105
darkhorn wrote: post #103

Earlier quoted context omitted.

What OS is this? Or what user interface?

Looks like Linux with Openbox: http://openbox.org/wiki/Openbox:Screenshots

I doubt that's Openbox. It would be one of the many tiling / dynamic WM's out there (DWM, Awesome, i3, Xnomad, etc).

As for which WM specifically, it would be impossible to say for certainty since every one of them can be configured to look like the other - so only the OP would know for sure.

I'd speculate that you're right about Linux, but only because the article exampled was about ArchLinux. However that could be a red herring and the aforementioned WMs would also compile on most modern *nixes (or at the very least, a few of the notable BSDs)

Re: Firefox 36.0 released

#112

Post by agapos »

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.

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

Restart-less add-ons have been around for long years, so if you see one that wants you to restart Fx, you can blame it on the addon's creator (I know there may be some edge cases where it is a must, but those are pretty rare).

Re: Firefox 36.0 released

#114

Post by cgtyoder »

sp332 wrote: post #40
kevincrane wrote: post #31

Earlier quoted context omitted.

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.

What's the preference name?

Re: Firefox 36.0 released

#115

Post by joshstrange »

sp332 wrote: post #90
joshstrange wrote: post #84

Earlier quoted context omitted.

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 chews through a lot of resources on my machine. Firefox is a lot lighter. And I think it will still be lighter since they're targeting a 2-process model instead of Chrome's (let me count) 17 that it just launched on startup.

Thank you! That makes sense, I still think I'd rather have per-tab isolation but I was genuinely interested in why FF would be preferable in this use-case.

Re: Firefox 36.0 released

#116

Post by cpeterso »

Shivetya wrote: post #53
h43k3r wrote: post #49

I recently switched back to Firefox from Chrome. They have done a nice job in speeding it up. My Chrome seems like more of a bottleneck than my internet connection.

my concern with firefox, at least on the mac, I tend to find video play back just stops whereas I can take the same video to Safari and have zero issues. I really wish there were a way to more easily identify if the problem is an addon or inherent to Firefox.

You can quickly test without add-ons by restarting Firefox in Safe Mode from the Help menu > Restart with Add-ons Disabled.

You can also restore Firefox to its default settings with Help menu > Troubleshooting Information > Give Nightly a tune up > Refresh Firefox button. It will uninstall your add-ons but retain your bookmarks, browsing history, and saved passwords.

Re: Firefox 36.0 released

#117

Post by cookiecaper »

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…

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.

Re: Firefox 36.0 released

#119

Post by sp332 »

cgtyoder wrote: post #114
sp332 wrote: post #40

Earlier quoted context omitted.

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.

What's the preference name?

dom.ipc.processCount

Re: Firefox 36.0 released

#120

Post by wasyl »

cookiecaper wrote: post #117
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…

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)
Post reply on HN