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.
As a python programmer for 15 years, I've never had a bug caused by indentation changing the logic.
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 literally only applies if you're invested heavily in the python community and have picked it up from there.
It applies if you want to be able to understand other people's code more easily.
So there's no long screeds about how you should never use tabs and only use spaces? And what's currently considered the "proper" amount of spacing? None of those things are obvious, and the space-vs-tab one is WAAAYY more of a minefield than K&R style braces vs GNU style (a particular form of horrendousness) or brace-on-a-new-line style.
The choice is not obvious, and there are MANY ways of doing it.
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.
What? No it doesn't. It's just a marginally different way of indicating blocks. If anything the lack of {} makes it shorter and so easier to nest.
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.
That inability to choose how to sculpt the visual aspect of code in Python is a monstrous shortcoming
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.
pretty much every function I write I can write loosely and then simply tell the editor to re-indent my code correctly
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?
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.
If you're an average bloke, your body is going to burn about 2000 kcal of energy per day just breathing, maintaining brain function, etc. - and that's a conservative estimate.
An hour's worth of intense cardio is about 800 kcal net, which again is rather conservative.
So if you're burning 2800 kcal a day, but only taking on 1600, you're running a daily deficit of 1200 kcal.
If you're losing any fat (i.e., not burning any fat or even muscle), where do you suppose that 1200 kcal of energy is coming from?
No, didn't you hear? Calories in / calories out is bullshit. Magical gut bacteria and fast and slow metabolisms and starvation mode and MUH GENETICS and fucking photosynthesis are all able to create energy out of nothing. That's why us fatties can't lose weight.
Maintaining multiple separate "versions" of a website hasn't been a thing for a good few years now. Anyone worth their salt will just serve the same HTML/CSS to all platforms, with rules specified in the CSS to re-arrange the layout on smaller devices. There are plenty of ready-made CSS frameworks that you that you can pick up, install and start using in seconds, and get a lot of this behaviour for free.
My content is now being punished not for its content, but for its presentation.
If you content is unique enough to stand on it's own, you're not being punished, and you won't be.
But if someone else comes along and offers a similar alternative that's formatted to be usable on a small-screen device, I'd rather use their site when I'm on my small-screen device, so I'd prefer Google rank their sites higher.
But I'm one guy running a website, not a company with budget for a web-designer.
Ironically enough, if you stayed away from trying to do complex CSS designs and just stuck to very basic HTML, your site would actually work better on mobile devices.
Slashdot Mirror
Don't sign your posts.
It is totally trivial to install a keylogger on Ubuntu
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
As a python programmer for 15 years, I've never had a bug caused by indentation changing the logic.
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 literally only applies if you're invested heavily in the python community and have picked it up from there.
It applies if you want to be able to understand other people's code more easily.
So there's no long screeds about how you should never use tabs and only use spaces? And what's currently considered the "proper" amount of spacing? None of those things are obvious, and the space-vs-tab one is WAAAYY more of a minefield than K&R style braces vs GNU style (a particular form of horrendousness) or brace-on-a-new-line style.
The choice is not obvious, and there are MANY ways of doing it.
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.
What? No it doesn't. It's just a marginally different way of indicating blocks. If anything the lack of {} makes it shorter and so easier to nest.
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.
That inability to choose how to sculpt the visual aspect of code in Python is a monstrous shortcoming
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.
abloo abloo copy and paste
Jesus Christ some of you guys really struggle with the utter fucking basics, don't you?
pretty much every function I write I can write loosely and then simply tell the editor to re-indent my code correctly
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.
If any part of your workflow unexpectedly strips out whitespace "for some reason", you've got bigger problems.
Yeah, he should just re-invent the wheel each time instead.
> works like a charm
> occassionaly hangs
Pick one...
> Critical systems
> GNOME 3
Aaaaaand here's where I stopped reading.
If you're an average bloke, your body is going to burn about 2000 kcal of energy per day just breathing, maintaining brain function, etc. - and that's a conservative estimate.
An hour's worth of intense cardio is about 800 kcal net, which again is rather conservative.
So if you're burning 2800 kcal a day, but only taking on 1600, you're running a daily deficit of 1200 kcal.
If you're losing any fat (i.e., not burning any fat or even muscle), where do you suppose that 1200 kcal of energy is coming from?
No, didn't you hear? Calories in / calories out is bullshit. Magical gut bacteria and fast and slow metabolisms and starvation mode and MUH GENETICS and fucking photosynthesis are all able to create energy out of nothing. That's why us fatties can't lose weight.
If 98% of obese people can't "follow the proper regimen". The thin people do. That's why they're thin.
get the poop transplant from the really fat dudes
All the shit transplants in the world won't change the fact that I burn more calories than I eat.
people like me
No, I'm pretty sure you're the only one with that particular brain issue.
Well shit, you've convinced me
Maintaining multiple separate "versions" of a website hasn't been a thing for a good few years now. Anyone worth their salt will just serve the same HTML/CSS to all platforms, with rules specified in the CSS to re-arrange the layout on smaller devices. There are plenty of ready-made CSS frameworks that you that you can pick up, install and start using in seconds, and get a lot of this behaviour for free.
My content is now being punished not for its content, but for its presentation.
If you content is unique enough to stand on it's own, you're not being punished, and you won't be.
But if someone else comes along and offers a similar alternative that's formatted to be usable on a small-screen device, I'd rather use their site when I'm on my small-screen device, so I'd prefer Google rank their sites higher.
But I'm one guy running a website, not a company with budget for a web-designer.
Ironically enough, if you stayed away from trying to do complex CSS designs and just stuck to very basic HTML, your site would actually work better on mobile devices.