I only skimmed the article, but does the new drive *not* match the specs? The specifications that Samsung publish, I mean - not what some dipshit "tech journalist" posts on their blog.

Don't sign your posts.

Wouldn't it be great if it wasn't, though.

It's insecure because .deb files can contain installation shell scripts which are executed as root each time an updated version of said .deb file is pulled down.

So by default, anyone who has write access to those repos has root on your box.

A better way would be some degree of sandboxing so a malicious package can't fuck with the entire system.

LTS to LTS distribution upgrades (e.g,. from 12.04 to 14.04) aren't usually possible on launch day. At least with 12.04 to 14.04, you had to wait until 14.04.1, which came a couple of months after.

Though to be honest, if your operation hinges on in-place distribution upgrades on production systems, you've got bigger problems.

An Ubuntu user getting snotty about "toy desktops".

Oh, the irony.

> Everyone who wants one, has one, and because the iPad is so over-priced

seems like they're priced perfectly then

I have. Once. Although I've only been programming in Python for about 8 years. It took me about 10 minutes to spot. I remember it so well because it was the first and only time I've made the mistake so far.

I honestly find it astonishing that everyone is throwing their hands up like whitespace-for-flow-control is the single stupidest thing to happen in computing. I've written a shitload of code myself, hacked on plently of people's projects, copied and pasted tons from random forums, mailing lists and websites and I cannot for the life of me figure out how anyone with actual motor control and a sensible toolchain could have had the kind of problems that justify the prevailing attitude here.

It applies if you want to be able to understand other people's code more easily.

The style guide written by the author of the language says "Use 4 spaces per indentation level." Regarding tabs vs. spaces, it says "Spaces are the preferred indentation method." It says this right at the top of the document. It's also in the beginner's guide of the official documentation, and is illustrated with numerous examples in the style guide itself. It doesn't get much clearer than that.

Properly-formatted Python code should be limited to lines 79 characters in length. Practically speaking, you can't use more than 3 or 4 levels of indentation in 79 characters. In most cases, deeply nested logic is spun off into top-level functions or methods. If you can't do this cleanly, it's a good indication you're doing something else wrong and should consider simplifying your approach. This also has the benefit of making that logic easier to cover with unit tests.

The interpreter itself doesn't enforce most of these rules because there are always edge-cases where breaking the rules makes things more readable. PEP8 states this right at the top. It still makes 99.9% of the rest of the code easier to work with though, so it's worth it.

Please post some examples of competently coded, PEP-8 adherent python that you find 'unclear', and explain what you think is unclear about it.

No, I think it's perfectly in-keeping with the rest of the zen of Python. Namely, there should be one (and preferably only one) obvious way to do something.

There's no bickering about bracing style, or special snowflake developers applying their own misguided style on everything. It discourages people from writing deeply nested, difficult-to-follow logic in favour of simple, flat code.

And when everybody sticks to the same conventions, it magically becomes a lot easier to read, understand, share, work on, learn from and contribute to everyone else's code.

Jesus Christ some of you guys really struggle with the utter fucking basics, don't you?

Or you can just write it properly in the first place and save yourself all the trouble? Does writing stuff 'loosely' really save you that many keystrokes?

Shit, you've got me there. I've never used source control that takes it upon itself to alter the whitespace in any files.

Probably because I don't use insane source control software.

If your grasp on your tools is so poor that "inadvertent" changes to *any* aspect of your source files is a legitimate problem, you shouldn't be writing production code.