I failed to notice that on the frost piss, but saw it somewhere below. I thought "wow, look at this mean hax0r, he's got his own anonymous handle on Slashdot". It turns out it's just Slashdot farting once again. How disappointing.
So they finally figured out that djb was right; it took them mere 10 years. If he only didn't have such a... personality. Maybe we would've had something sane by now.
Intel's integrated graphics performance has been pretty progressively worse ever since switching from XAA, and rather abysmal ever since Xorg 1.5. Since then every release of X/mesa/xf86-video-intel made it even worse. Hopefully this release brings the entire GEM/UXA/KMS/whatever stack to a usable state. All this on a 945GM.
What's your experience with it so far? I'll try it out myself in a few days, but I'm eager to hear the results...
Ligesh has (had) a blog with an about page. Sounds a bit f**** up.
A number of hosts have been hit by this, see e.g. this post at WHT. The software itself is apparently closed source (i.e. obfuscated source). Based on what I read, it was also quite cheap (speculations were ~50 cents for a single VPS), so most budget VPS providers used it.
This includes 2host, where I got an account a few days back. A few hours later I got an e-mail saying they disabled the HyperVM panel. Nice.
I'll get off your lawn since I only started using Linux since 1.0.8;)
Might wanna try out Arch Linux. It kind of reminds me of Slack - just with a proper package manager and without an opinionated (B)DFL. BSD-style init, everything is generally real easy to configure by hand, and the packages are pretty close to vanilla. They are binary so usually you don't have to waste time compiling them yourself, but when you need to, it's real easy - their "automated build system" (ABS) is mighty cool. The base install is minimal, but they're not too obsessed with freedom, so you get a completely usable desktop with the default repos, and there's also a huge community-provided repository.
It's a rolling release though, so stuff does occasionally break. Still, by far my favorite modern desktop distro (I also tried Fedora, Ubuntu and OpenSuSE)
There were already news of something similar in March.
Judging by the currencies the malware operates with, it seems the "Eastern European countries" are Ukraine and Russia. Does anyone know if it's Diebold again?
And putting aside the incredibly logical choice of the OS, any idea on how this gets installed on the ATMs in the first place?
1- Any time there's a new feature you need to code a version with and without it, or you're cutting out the bulk of users still on the old version of code. PHP's more gradual approach is no different.
Maybe we disagree with the concept of a "feature". A new feature was adding a different syntax for constructors in PHP5. You can choose to use it, or you can choose not to use it. A "feature" that breaks my code is not a feature, it's introducing backwards incompatibility. Backwards incompatibility = bad. Furthermore, the behaviour of my code changes from one installation to another. That's also not a feature, that's lack of portability.
3- It's the implementation not the feature. If they enable it by default they'll have to stick with the implementation and maintain backwards compatibility. If they slow acceptance a bit, they have a chance to make changes without effecting as many users. For instance changing argument order before it would majorly break backwards compatibility and become an idiotic thing to change.
There's no such thing as breaking backwards compatibility "just a little bit". You either break it or don't break it. And any time you create a public API of any sort you are making a commitment to keep it stable. If you're breaking a commitment you better have a damn good reason for it, and make sure that you run out of other viable options.
Besides, if they're unable to create a reasonable interface to a feature that's been present in most programming languages for a decade, they should perhaps think of switching careers.
all the subatomic particles in your body will suddenly decide to move together through the wall behind you into the ladies room on the other side
I can already see that making a fine closing in the court room. "And that is what happened, ladies and gentlemen of the jury, unlike what the prosecution would like you to believe!"
Version X+1: feature is optional, developers can start coding apps with it, and also maintain apps that do not yet support it
Right. Except that it's completely out of my hands as a developer. It means that, if I'm to build a distributable app, I need 2 versions of the same code. Which is a Bad Thing. You know, DRY and all that jazz.
Magic quotes was an unfortunate feature that existed when the language was first created.
Are you sure about that? I don't know the history of PHP (I only started using it some 5 years ago) but I don't think that magic quotes existed when PHP was first created. It seems to me as if it was just monkey-patching of a gaping hole caused by a combo of featureless DBMS and the incompetent average developer.
This sort of phased plan also has the major advantage of not making a feature mandatory or default before it's been well tested and determined to indeed be worth keeping around and making mandatory.
Ah. So PHP devs need to determine whether having Unicode support is worth keeping around. Great. And they're also wondering if it's worth making mandatory, while they introduce a bunch of other backward incompatibilities. Makes sense.
In the finest tradition of PHP, they made Unicode behaviour dependent on a setting. Have these people learnt nothing from the past? magic_quotes anyone? Bleh. All languages have their warts, but the amount of bad design decisions in this one is just staggering.
Uncoordinated diversity leaves a lot of people to fend for themselves. Having unity-in-diversity (a common strength across systems and organisms), however, might well solve the problem.
Now you wouldn't happen to hold a degree in politics or economics, would you?
I consider myself to be an expert skier as well, but I'm not sure your analogies are valid. Skiing injuries are generally the result of a single accident, while I guess running injuries mostly belong to the repetitive stress category.
While I appreciate your attempt to bring up a car analogy with Formula 1, the same objection could be made to that one as well.
I suppose that an analogy that could hold would be the one with tennis. Generally, tennis racquets that the pros use tend to be heavier and put more strain on the joints. Marcelo Rios was the world #1 while using a heavier racquet, but after elbow injuries he switched to a lighter one and never regained the same ranking again.
Dunno where you live, but your CS students must have a load of time on their hands if they're able to enter the said data for every settlement in the entire world.
To reply to myself:) But an example just came to my mind, think of a point on the surface of a torus. You can describe the location of any single point on it with two numbers, i.e. two angles (one from the center of the torus, and one from the center of the torus "tube"). If you describe it like this, then both of your dimensions are finite.
Slashdot Mirror
I failed to notice that on the frost piss, but saw it somewhere below. I thought "wow, look at this mean hax0r, he's got his own anonymous handle on Slashdot". It turns out it's just Slashdot farting once again. How disappointing.
So they finally figured out that djb was right; it took them mere 10 years. If he only didn't have such a... personality. Maybe we would've had something sane by now.
...SDLC lifecycles
I on the other hand believe that the paramount need is to teach them the principles of DRY repeat yourself.
Intel's integrated graphics performance has been pretty progressively worse ever since switching from XAA, and rather abysmal ever since Xorg 1.5. Since then every release of X/mesa/xf86-video-intel made it even worse. Hopefully this release brings the entire GEM/UXA/KMS/whatever stack to a usable state. All this on a 945GM.
What's your experience with it so far? I'll try it out myself in a few days, but I'm eager to hear the results...
Ligesh has (had) a blog with an about page. Sounds a bit f**** up.
A number of hosts have been hit by this, see e.g. this post at WHT. The software itself is apparently closed source (i.e. obfuscated source). Based on what I read, it was also quite cheap (speculations were ~50 cents for a single VPS), so most budget VPS providers used it.
This includes 2host, where I got an account a few days back. A few hours later I got an e-mail saying they disabled the HyperVM panel. Nice.
I'll get off your lawn since I only started using Linux since 1.0.8 ;)
Might wanna try out Arch Linux. It kind of reminds me of Slack - just with a proper package manager and without an opinionated (B)DFL. BSD-style init, everything is generally real easy to configure by hand, and the packages are pretty close to vanilla. They are binary so usually you don't have to waste time compiling them yourself, but when you need to, it's real easy - their "automated build system" (ABS) is mighty cool. The base install is minimal, but they're not too obsessed with freedom, so you get a completely usable desktop with the default repos, and there's also a huge community-provided repository.
It's a rolling release though, so stuff does occasionally break. Still, by far my favorite modern desktop distro (I also tried Fedora, Ubuntu and OpenSuSE)
But can they smell it if you encrypt the contents? HA!
There were already news of something similar in March.
Judging by the currencies the malware operates with, it seems the "Eastern European countries" are Ukraine and Russia. Does anyone know if it's Diebold again?
And putting aside the incredibly logical choice of the OS, any idea on how this gets installed on the ATMs in the first place?
(what's the opposite of n00b anyway?)
u can use l33t, 1337, 0r 3v3n 001011011111, but tehn again, how would u kn0w, suxxor?
I knew zhish breshal... zhing doeshn't work!
1- Any time there's a new feature you need to code a version with and without it, or you're cutting out the bulk of users still on the old version of code. PHP's more gradual approach is no different.
Maybe we disagree with the concept of a "feature". A new feature was adding a different syntax for constructors in PHP5. You can choose to use it, or you can choose not to use it. A "feature" that breaks my code is not a feature, it's introducing backwards incompatibility. Backwards incompatibility = bad. Furthermore, the behaviour of my code changes from one installation to another. That's also not a feature, that's lack of portability.
3- It's the implementation not the feature. If they enable it by default they'll have to stick with the implementation and maintain backwards compatibility. If they slow acceptance a bit, they have a chance to make changes without effecting as many users. For instance changing argument order before it would majorly break backwards compatibility and become an idiotic thing to change.
There's no such thing as breaking backwards compatibility "just a little bit". You either break it or don't break it. And any time you create a public API of any sort you are making a commitment to keep it stable. If you're breaking a commitment you better have a damn good reason for it, and make sure that you run out of other viable options.
Besides, if they're unable to create a reasonable interface to a feature that's been present in most programming languages for a decade, they should perhaps think of switching careers.
all the subatomic particles in your body will suddenly decide to move together through the wall behind you into the ladies room on the other side
I can already see that making a fine closing in the court room. "And that is what happened, ladies and gentlemen of the jury, unlike what the prosecution would like you to believe!"
Yes, it's also what made Javascript so painful before the dawn of the toolkits.
Except that I'm not sure if it qualifies as "the worst practice" from a developers point of view, since a developer has no control over it.
Version X+1: feature is optional, developers can start coding apps with it, and also maintain apps that do not yet support it
Right. Except that it's completely out of my hands as a developer. It means that, if I'm to build a distributable app, I need 2 versions of the same code. Which is a Bad Thing. You know, DRY and all that jazz.
Magic quotes was an unfortunate feature that existed when the language was first created.
Are you sure about that? I don't know the history of PHP (I only started using it some 5 years ago) but I don't think that magic quotes existed when PHP was first created. It seems to me as if it was just monkey-patching of a gaping hole caused by a combo of featureless DBMS and the incompetent average developer.
This sort of phased plan also has the major advantage of not making a feature mandatory or default before it's been well tested and determined to indeed be worth keeping around and making mandatory.
Ah. So PHP devs need to determine whether having Unicode support is worth keeping around. Great. And they're also wondering if it's worth making mandatory, while they introduce a bunch of other backward incompatibilities. Makes sense.
In the finest tradition of PHP, they made Unicode behaviour dependent on a setting. Have these people learnt nothing from the past? magic_quotes anyone? Bleh. All languages have their warts, but the amount of bad design decisions in this one is just staggering.
The problem is not (necessarily) the sum - access to means of electronic payment is often severely limited in the 3rd world.
Except that it would also hamper the ability of people in the 3rd world to submit their proposals.
Great, just that selecting from a few thousand of drone bees can be somewhat harder.
Uncoordinated diversity leaves a lot of people to fend for themselves. Having unity-in-diversity (a common strength across systems and organisms), however, might well solve the problem.
Now you wouldn't happen to hold a degree in politics or economics, would you?
assuming it has a relatively low flash temperature (like wood, paper, even plastic or paint).
But does it work on human flesh?
Please advise.
Kind regards,
The World Madmen Organization
Unfortunately, from TFA it seems that your CT scanner would need to have a two-mile linear accelerator behind it.
I consider myself to be an expert skier as well, but I'm not sure your analogies are valid. Skiing injuries are generally the result of a single accident, while I guess running injuries mostly belong to the repetitive stress category.
While I appreciate your attempt to bring up a car analogy with Formula 1, the same objection could be made to that one as well.
I suppose that an analogy that could hold would be the one with tennis. Generally, tennis racquets that the pros use tend to be heavier and put more strain on the joints. Marcelo Rios was the world #1 while using a heavier racquet, but after elbow injuries he switched to a lighter one and never regained the same ranking again.
WTF dude. If there ever was a /. post worth of the "news for nerds" title, this is one.
Absolutely freaking awesome.
Dunno where you live, but your CS students must have a load of time on their hands if they're able to enter the said data for every settlement in the entire world.
To reply to myself :) But an example just came to my mind, think of a point on the surface of a torus. You can describe the location of any single point on it with two numbers, i.e. two angles (one from the center of the torus, and one from the center of the torus "tube"). If you describe it like this, then both of your dimensions are finite.