Because each Linux vulnerability is reported for multiple distributions. And because Linux vulnerabilities are found faster and therefore fixed faster. However you want to spin it, Windows is the one getting successfully exploited in multiple ways, so that new Windows vulnerabilities are hardly news any more, whereas its big news any time a hole shows up in Linux, and then very few fall victim to it.... partly because of the early and widespread disclosure, but more because Linux vulnerabilities typically require local access, login shell, etc. Whereas a dodgy flash file is often enough to take out a Windows box.

And it's still leaky as a sieve. That speaks to basic design flaws.

Yah, shove it. I typically have 500-600 tabs open and I like it that way. Just make it work.

I just grabbed the opera .deb package and installed it, total elapsed time roughly 30 seconds, and it is suh-weet. Thanks to whoever posted this for the suggestion. Chrome is really pissing me off these days. Firefox still likely be be my main browser because of vastly superior tab handling and actual open source project.

Talk to me about IOPS -- Input/Output operations Per Second -- or don't pretend you're talking to me about performance.

Not saying this isn't actually really exciting, but that's the metric in at least 90% of use cases.

World's largest *unclassified* tunnel boring machine.

My sense is that the MEAN Stack (Mongo, Express, AngularJS, Node) is sort of winning. There's some packaging of it over at mean.io.

Personally, I'm really getting interested in Meteor (www.meteor.com). Watch the videos, and realize I saw a smart non-coder go from zero to *ridiculously* interactive site design in three months.

Especially if those automated software deployment packages like SCCM are Microsoft products.

Thanks for the bug report :)

Those shiny distributed file systems run on top of boring local filesystems.

Tux3 is a better design. Tux2 was more along the lines of ZFS and Btrfs, that is, multiply-rooted trees sharing subtrees. Tux3 is a single tree with exactly one pointer to each extent. Considerably easier to check and repair. Of course we need to see if it turns out that way so please stay tuned.

Indeed, different aims. Tux3 has the modest goal of being a light, tight and fast filesystem without ambition of also being a volume manager.

No really.

I took a pass at Python 3 a while back. The amount of hoops I needed to jump through, to deal with compilation errors around Unicode handling, was terrifying. It was simply a poor user experience.

Python 2.7 just works. Sure, it's a nightmare past a certain scale point. But until you get into the dregs of OO it really is executable pseudocode.

Python 3 is some other language that lost that property.

The big problem is that we don't ship languages with telemetry that reports when they fail to work. So things that are completely obvious to outsiders never make it to inner circles. Not that I can really see any way for Python 3 to mend its errors.

Summerfolk? I can hardly believe someone else knows that book.