XP comes with a perfectly good command line ftp client, ported from BSD.

What's weird is that Intel was in the ARM business for a while, before selling XScale to Marvell in 2006, just as it was taking off. Maybe the prices were getting too competitive.

Xubuntu at home (Windows-free), XP at work :c

MySQL's had a strict mode since 2004 to reject invalid data. They didn't make it default until late 2012 though in 5.6.8, and I couldn't find what the MariaDB default is (short of downloading the source and looking). Even then, they only it in the default config file, so manual or distro-specific configs that omit the setting will fall back to the old truncation mode.

All these people upset with digg v4 are just a vocal minority trying to ruin the experience for everyone else.

I never found Typescript's output to be that hard to read, since it preserves comments and changes the code very little apart from rewriting class definitions.

You can enable source maps, which the Firefox/Chrome debuggers can use to show you the original code when debugging compiled code. And some minifiers like UglifyJS can transform source maps to continue working after minifying.

I'd miss Calc's NLPSolver, but that's about it.

The ones I get stuck with always seem to require Java 1.4.2, so any new breaking changes are irrelevant.

The software did its job. But they buy their maps from at least a dozen other companies and one of them made an easy mistake, like marking a private road as public. That's not quite the same as a wheel falling off.

I need to set up a dead man's switch that posts denials of my demise.

Every update I redisable all the nvidia services, startup tasks, and shell extensions, breaking nothing of value.

For one, it creates lots of temporary files for every file it scans, trying to extract them like an archive whether they really are or not. That's why it scans so slowly, and will thrash your hard drive even if you're scanning files elsewhere, like over the network.

Ext3's commit interval was one of its best features.

Sure, it doesn't have to make guarantees when the app doesn't explicitly sync, but losing data 1% of the time in an outage is better than losing data 99% of those in those cases.

Whenever I saw people complaining of losses in XFS that wouldn't have happened in ext3, the "doesn't have to guarantee unless synced" thing was brought up as an excuse.