Laptops because they do not have the airflow nor the more heavily built components of desktops, and should be shut down when not in use IMHO. Laptops by the simple fact that they do get moved around are orders of magnitude more likely to suffer failures just because they are subjected so much more dirt, impact, vibration, extremes of temperature, than desktop machines. Not to mention the greater possibilities for theft. You are probably more likely to have a failure due to these factors than leaving it on.
As much as I hate to say this, you are the poster child for disaster. Depending what kind of freelancer you are, you have a variety of needs for backups both of data as well as spare hardware.
For example, if your hard drive in your machine failed right now, how much work in progress would you lose? Do you have some kind of ongoing backup regimen?
What kind of losses would you experience if your laptop died right now with or without data loss? Mobile computer dependent professionals need to look at computers in terms of acceptable losses not in preservation of investment. Depending on your power needs you might be better off with dropbox syncs between two machines to minimize unplanned downtime in the event of loss or failure. Things like a broken laptop screen are not going to be something a typical computer shop has parts on hand for for example.
Sorry if I started lecturing, I have had several customers lose or break laptops and then go on lamenting the unfairness of the universe when they could not work for several days.
Firefox on my old work laptop was a serious performance problem if left on for extended periods of time. I went through a process of elimination, instead of leaving all programs running I would end 1 and leave the rest running. When Firefox was not left on overnight performance was fine the next day, all other programs made no difference. I repeated it many times, enough I was satisfied Firefox was the problem.
You appear not to know what you’re talking about. Memory leaks are a real problem in software in general, and with Firefox in particular. It’s arguably been the single biggest technical issue they’ve had to deal with in the last few years. It’s been often cited as the reason people have been moving away from Firefox to Chrome.
Here, for example, is a dev team email about them from John Stenback, one of the lead Mozilla developers who’s been working on the project since it was Netscape. The email was sent less than a year ago.
Just google for “Firefox memory leak” and start reading.
That’s absurd.
When a laptop is asleep, there is no significant power dissipation (my laptop can stay asleep for over a week, and still have some battery power left), and the hard drive is parked and off.
My recommendation: just close the lid, wait for the drive activity light to go off, and pack your laptop. I almost never turn my laptop off - it is either working or asleep.
Even if that is still true, it doesn’t appear to permanently lock up memory; in other words, the memory is freed when you close Firefox (as with my experience with the UPS software I mentioned). That leads to the question of why people leave it running all the time; Firefox allows you to easily restore your previous session so you can just close it when you are done and then click on “restore previous session” when you start it up again, at least on the default start page. For comparison, when I stop using my computer, even when just in sleep mode, I have all apps closed (of course, that still leaves many processes like AV running, but with Windows 7 I haven’t ever had any performance problems related to this, though my previous computer with XP started acting funny after a few weeks without a reboot).
That may be the case. I haven’t used Firefox for a while (because it used to leak all over the damned place and I switched to Chrome), so I’ll take your word for it.
“This used to be true, but new versions of Firefox no longer suffer from major memory leaks” would have been a lot clearer and more helpful than “that is patently false”. Not everyone is using the newest version.
My “process of elimination” experiment was 2 months ago - also in 2012 (on a fairly recent version of Firefox but not THE most recent version).
You know, most reasonable people can relate to statements like “many of those problems have been fixed in the most recent version” - but when you make statements like “patently false”, it tells us that either you are emotionally biased by the subject or simply unaware of the actual facts.
Don’t - I’m on Firefox 10 (which I see as of two days ago is no longer current), and I have seen no particular improvement in the gradual creep of its memory footprint. This may not technically be leakage - the browser might be tracking the memory just fine, but it’s not freeing it to the OS.