Living in a slum is good because it's environmentally friendly and uses less resources? He may as well argue that's it's even more environmentally friendly to die young.

I find 9.10 is working faster than 9.04. It boots faster and the interface is a little faster. The only issue I have is wxmaxima crashes constantly. I can't even do a sqrt(4); without crashing. I'm hoping patches will take care of everything soon.

Our company finally moved away from windows software RAID because of problems. One drive would fail, then while rebuilding we'd find errors on the second drive. Usually bad sectors that couldn't be read. Windows 2003 doesn't do any SMART monitoring so a drive can start failing and you'll never know until you try to read/write data to that part of the drive.

On my linux server I have smartmontools checking the drives nightly which has saved me once so far. I can't find an equivalent for windows so we've moved to hardware which can check for failing drives.

Ever since Open Office 3.0, I've been able to completely move away from MS Office 2003. I can create word documents that look exactly the same in MS Word 2003, like they do in OO 3.0. Now I can easily exchange documents between coworkers and they have no idea I'm using OO.

I work in aweful world of end-user IT for small businesses. These people are INCREDIBLY picky about how their word, excel, etc documents look. They are also incredibly slow at learning how to use office software. Switching these people from MS Office to OO is nearly impossible. People HATE HATE HATE software with a different interface. Most Office 2003 customers won't touch office 2007 for that exact reason. If OO were improved to the point that it could simulate MS Office so people could easily switch over, OO could take over. I think replacing MS Office with OO is one of the Big Steps linux needs to take to push windows off the desktop.

Too true.

I want to take it myself so I can feel all smu.... err... ensure that I know enough about our great nation here.

On a scale from 1-10, how fond are you of federal prison?

TFA acknowledges this problem.

""Cloning animals by nuclear transfer provides an opportunity to preserve endangered mammalian species," they wrote.

"However, it has been suggested that the 'resurrection' of frozen extinct species (such as the woolly mammoth) is impracticable, as no live cells are available, and the genomic material that remains is inevitably degraded," they said."

But who would resort to such extreme measures as reading the article?

Hydrogen peroxide powered rocket packs fly for around 30 seconds, because they have a specific impulse of around 125, meaning that one pound of propellant can make 125 pound-seconds of thrust, meaning that it takes about two pounds of propellant for every second you are in the air. Mass ratios are low for anything strapped to a human, so the exponential nature of the rocket equation can be safely ignored.

A pretty hot (both literally and figuratively) bipropellant rocket could manage about twice the specific impulse, and you could carry somewhat heavier tanks, but two minutes of flight on a rocket pack is probably about the upper limit with conventional propellants.

However, an actual jet pack that used atmospheric oxygen could have an Isp ten times higher, allowing theoretical flights of fifteen minutes or so. Here, it really is a matter of technical development, since jet engines have thrust to weight ratios too low to make it practical. There is movement on this technical front, but it will still take a while.

John Carmack

Check out page 3 of the executive summary. In Jan-Jun of 07, they found that 89% of web vulnerabilities were in ActiveX plugins in IE. 1% of vulnerabilities were in Mozilla extensions.

I think we have a clear winner here...

I think it depends a lot on how many systems you use, both now and in the future, and also your rate of learning.

If I'm a new Java programmer I'll probably get more out of Eclipse than vi or Emacs; if I'm using Windows I might get more out of Visual Studio than vi or Emacs. But that's just in the short term. In the long term, the language and operating system might change, but the need to work on text files is likely to still be there. If I'm using multiple languages or OSes now, or if I expect that I'll be using different languages or OSes in the future, it means I'm likely to change IDEs. Each time I change, I'm learning from scratch. This means I don't get more than a decade of becoming an expert with one editor; instead I learn the most common tasks but not the advanced features.

With vi(m) or Emacs, I get something that's not optimized (specialized) for one environment, but instead something that's general-purpose and adapts to many different systems, and I can carry what I learn from one system to the next. I've been using vi and Emacs on Solaris, OS/2, Linux, Windows, Mac, with C, Scheme, C++, Java, Ruby, Python, Perl, SML, and many other languages. I could've used Visual Age on OS/2, but most of what I learned would not have been that useful when I switched to Eclipse on Linux, and most of that would not be useful when I switched to Visual Studio on Windows, and most of that would not be useful when I switched to XCode on Mac. Instead, I'm using a tool that's less optimal for my current needs, but it's something that I can keep using for other needs.

It extends beyond programming to my editing of text files, email, messages for newsgroups, HTML, my diary, my calendar, blogs, XML, config files, etc. Do you use Visual Studio for editing your blog, or do you use a different editor? Do you use yet a different editor for HTML? For email? I think it's a reasonable way to go but I find that I only use the simplest editing functions when I use lots of editors, because I can't count on features being available as I switch from one context to another.

It's a tradeoff, and I don't know for sure whether it's better to be a novice with specialized tools or an expert with a single general-purpose tool. I'd consider vi(m) and/or Emacs if you're editing a whole lot and expect to be editing on many different systems, languages, etc. I'd stick to IDEs if you're using one system a lot and don't expect to switch often, or if you don't edit enough that there's any benefit to learning vi(m) or Emacs.