Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:Tape (Score 1) 484

Your second point isn't 100% right, modern tape drives have two features that more or less eliminate "shoe-shining". The first is that the tape drive can usually run at multiple speeds, sometimes as low as 1/3 of it's headline speed so if you can't keep up it adjusts. But the most important feature is a huge buffer, several seconds of write time between the OS and the tape surface. With both of these in place the "shoe-shining" is minimal. (eg: a quarter second backtrack every 5 seconds; as compared to the old QIC drives where you could easily end up with the equivalent of twenty passes.)

PS: If you happen to have an old tape drive that doesn't have a huge buffer it can easily be done in software.

Comment Re:At least the Perl crowd is trying, (Score 1) 130

RHEL5, released March 14, 2007, uses Python 2.4.3, which was released March 29, 2006. Given a reasonable package-freeze/testing/bugfix cycle, using this version seems about right. Also, Python 2.5.0 was released September 19, 2006 -- I know I wouldn't want to make a potentially major jump for all my system tools before publishing a major distro release.

Perhaps you should rethink the presentation of your point next time -- given what you've said already concerning RHEL5 and Python2.4, you should also be saying "RHEL5 uses Linux 2.6! That was released back in 2003!!!! ZOMG!!!"

In re: Python 3 migration, moving to the Python 3 series presents FAR bigger issues than addon-distribution, namely the changing and/or removal of some particularly widely-used items from Python 2.

I will agree with you that distribution of third-party modules can be annoying in Python, but that's not necessarily the Python developers' problem. Why should they be implicitly responsible for something that is third-party? Just because another platform is doing it? C'mon, that's a flimsy argument at best.

Slashdot Top Deals

You're using a keyboard! How quaint!