There are many more reasons than just the random redirects to the beta site, to prefer Soylent News to /. You should check it out.

sudo: try: command not found

On the flip side, spending six weeks fixing an issue on a single server running a non-critical, non-time-sensitive service which occurs once or twice a year and is 100% worked around by a reboot probably isn't an efficient use of your time.

In the long-term, it is. If you let issues like that continue to exist, then you'll get stuck with an unnecessary proliferation of servers, with each running just one service, so rebooting one doesn't take the others down.

Not to mention that you'll find that you get stuck maintaining multiple, overlapping services, because the first one wasn't reliable enough for the tasks some department decided to bring-in, later.

And also, I don't think I've ever seen a service that was non-critical and non-time-sensitive. Whatever it is, people won't even try to use it until the very last minute, when they need it to work immediately. It could be a damn web page that just hosts the phone extension list, and because HR needs to call someone about something simple, at 5pm on Friday, that server is now delaying everyone's paychecks. EVERYTHING ends up being varying degrees of critical.

I oversimplified the explanation a bit...

Here it is in nicm@'s words:
"In particular, being able to share a single window between multiple terminals, with other windows in the same session but entirely separate. Adding this to screen was implausible"

http://undeadly.org/cgi?action...

"Reboot does not fix anything, it just hides things".

That's not specific to rebooting... It's more a question of doing root-cause analysis, versus quick bandaids. I'm firmly in the RCA camp, but sometimes it's the companies that are to blame, rather than the individual admins. Some companies are heavily slanted towards always getting the quickest possible workaround, rather than ever actually finding and fixing the problem. It's one of those false-economies, like counting lines of code and similar.

For my use cases, I could not find a compelling reason to use tmux

Obviously if you've been limiting yourself to the features of "screen" for many years, you're not going to think you need the added features of "tmux"...

A big one is sharing:
"window can be linked to an arbitrary number of sessions". If you or somebody else has a screen session open, you don't have to detach it from their terminal to see what's on it. You can just attach it to your terminal as well. Works great when you've got a session attached to your desktop, then want to access it on your laptop/tablet/phone/etc. The tmux session will even change geometry to match the smallest terminal window.

Being more lightweight and responsive is good. Saner keys for some functions, like ctrl-a pg-up to access scrollback. And just the fact that it's still getting active development is an important feature.

Older coders are sitting around doing nothing, and there's gold in them thar hills.

It'll cost you an order of magnitude more to provide them health insurance... Maybe double or triple that again, if the plan includes aging wifes as well.

And while they might be very good, I wouldn't expect them to be as willing to do on-call rotation, put in extra hours when deadlines loom, not use their vacation days, etc.

It's not a bad idea at all, but there's sure going to be some major downsides to a company with predominately older people.

(I'm over 50, have been looking for work for a while now, and I'm getting nothing; no interviews and certainly no offers. I have a lot of experience and a good work ethic, but it does no one any good if the companies routinely dismiss anyone with more than 2 pages of resume experience,

You're doing something wrong... Nothing on your resume has to show your age, and you certainly don't have to have more than 2 pages, just because you have lots of experience. Resume writing 101. Limit yourself to the latests 3 jobs, or so. Nobody wants to look through a 10-page resume, so if you don't have good-stuff on the top page, recruiters won't bother.

since they are seen as 'too expensive' to hire).

Lots of recruiters ask for your salary requirements up-front. I generally refuse to answer, but if you low-ball it, you'll do just fine. Hell, my last company, though predominantly young, with lots of H1Bs, had several grey-haired programmers, and I recently hired an older gentleman myself, who was only looking for work after his company (where he put in 25 years) went out of business.

This is why you keep an image up to date to deploy Windows with the updates already installed...

I'm probably just strange, but the start screen is the issue I have with Outlook 2010 where going to the file menu totally covers up all the e-mail. I still use find and run robot myself, on windows 7. It's hard to explain, but the total context switch between what I'm doing and running another program really depends on what I'm trying to do.

If I'm on a web site, and need to run my password manager to log in, it's horribly disorienting to lose the view of the website to just start a password manager. Or if I'm working on my banking website and need to run calculator, it's really disconcerting to me to lose the banking view while trying to start calc.exe. I can sort of do those things in the background of my thought process.

Now, if I'm totally starting a new task (say launching a video player to watch a movie), then overlaying the whole screen isn't a big deal - I'm planning on totally context switching. But if I'm just checking to see if an app I need is installed, or I just want to start a helper app, I don't want to "lose my place" in that way.

You do know that Putty has an installer if you want?

Wouldn't your status information be in your monitoring system? I mean, rather than sucking cycles to show a tile on a desktop on my server, I'd just like an e-mail when something gets out of spec, and an overview of a whole set of servers in a WebUI if I want to look actively...

I'm sorry, but I see enough Windows 7 "slowing down" for no particular reason at work to think that it may be marginally better than XP in terms of not bitrotting itself to death, but it's a marginal improvement.

We've replaced the vast majority of Windows XP computers with Windows 7, but in a number of cases recently, it's been wholly driven by IT, and involves throwing out existing hardware because it can't run Windows 7 x64 without stupidly priced RAM upgrades (DDR2 is apparently quite expensive now). The upgrade to Windows 7 has been great for IT - making parts of our jobs easier, giving us easy tickets to close - but from a business perspective, it's a total loss. The computers were serving a need perfectly well, and replacing them with more expensive newer hardware is a waste of money except for the security issue with EOL.

If you get married that should be entirely between you, your God(s), who ever else attends where you warship, and that's it.

I am interested in learning the details of your denomination.

I'm guessing he either belongs to the church of Dvorak, or the church of autocorrect.

I'd also REALLY like to see where you are pulling your reliability numbers from.

There are publicly available uptime tracking web sites.... Always dominating the top of those list is OpenVMS, thanks to its (ancient) built-in clustering technology.

Linux isn't even old enough to compete...