It's blizzards latest game where Orcs and Humans battle it out over the high seas......I heard its going to be bundled with Doom 3 this summer.
I thought it was the Protoss and the Zerg battling it out on the high seas, to be released in a bundle with Duke Nukem Forever this <whenever>.
What about the physical characteristic changes?
on
Robocones
·
· Score: 4, Interesting
Normal road cones weigh about nothing. (A couple of pounds of soft plastic. Designed to fly out of the way or crush down when struck by a vehicle.)
Does adding an RF receiver and motors add weight and rigid bulk to the cone, making it more damaging to hit?
It's bad enough if you hit one of the road cones with the battery-powered flashers on the top, but that weighs very little. I hope the folks designing these keep impact-safety factors in mind.
Outsourcing your attack to overseas cracker groups. Say, the same fine people who keep attacking online betting parlors for extortion. That would make it harder to track down, particularly if they're using zombie-nets.
What if the hackers ARE the current administration? What's your guarantee that law enforcement will investigate its own bosses? (Or have we already forgotten Watergate?)
If you're caught, you' pretty busted. But the likelihood of being caught aren't astronomically higher than your chances if you futz the old-sk00l election process in the usual time-honored ways.
I said that part of the war was securing access to their oil,
Your assertion...
which is true.
Not proven. Probably not provable. So all we have is your unsupported assertion. Repeatedly asserting an unproven assertion doesn't constitute proof.
And seeing that a very large portion of the US economy runs on oil, having access to Oil is a good thing from a stratigic point of view.
As an isolated statement, possibly true, but fails to take into account the costs of that access. Both short-term (lives, property, political standing of current administration) and longer-term (strained international relations, future loss of life to terrorism or war subsequent to those strained international relations, the judgement of history).
I'm not arguing that you're wrong. I'm arguing that you don't really know whether you're right, not in any fashion meaningful to anyone else but yourself.
The impression you give with your stance is that you're positive about these beliefs. "Positive" is "wrong" at the top of your lungs.
I'm trying to figure out how strong your cooler mounts will have to be in order to support about a cubic meter of "high-efficency motor." It's hard to judge, but it looks like about 20 or 30 Kg of motor to me.
Not much of a reach to imagine my WUSB flash pocket drive crashing your WIN XP++ session when I walk into the room. Hell, how are they going to keep this from becoming a wireless DoS attack, crashing systems from afar with tailored WUSB negotiation exploits and high-powered WUSB transmitters? Or will all WUSB drivers be perfect now?
Never let principles stand in the way of accomplishing the mission. If the missions calls for Java, render unto Sun what is Sun's and carry on, dammit.
High-pitched mechanical sounds carry a connotation of machinery operating "out of control", or running faster than it should. I'll put it this way. If you walked into, say, a widget factory, and heard the machines cranking away with a low rumble, wouldn't you feel more comfortable than if they were generating a constant high-pitched whining?
That's an interesting insight. (I don't have mod points, so I'm word-modding. Mod Nazis, bite me.)
The reason mechanical bits sound "wrong" when making high-pitched sounds is that the usual source high-pitch sound in conventional mechanics is friction. Friction sound means lubrication failure, usually followed quickly by breakdown (perhaps at speed, with attendant spontaneous ballistic self-disassembly).
If I understand correctly, the high-frequency components of the "problem" sound of maglevs have absolutely nothing to do with friction. Au contraire, it has to do with frictionlessness (non-contact magnetically-maintained air bearing). So it makes no rational sense that perceived discomfort has anything to do with mechanical breakdown.
But that doesn't mean it's not so. I imagine the reaction to the sound is visceral, not rational, so explaining that "No, it's not breaking down, it always sounds like that" won't help.
I don't see how hiring a public relations firm is a meaningful separation of enjoined action (continued public unsubstantiated allegations of copyright violation) from enjoined actor (employees of SCO). In other words, if I'm legally prohibited from doing an act, aren't I usually legally prohibited from hiring an agent to do it for me?
I guess not always. But it seems like it sure should have been in this case, and if the settlement had that loophole then shame on Univention's lawyers for letting that slip.
Another interesting point, too. According to the Groklaw article about the settlement, the per-offense fine is only about 10,000 euros. That's not a lot, really; just a tiny extra bit of marketing budget for the FUD machine. Is that really all the teeth the settlement has?
(And try installing the native Java from BSD ports - several hours of pure joy!)
I'm not sure whether to mod you -2 BSDTroll or +1 BSDFunny. However, I'll comment instead. (Commented earlier downthread, so it's already a foregone decision, but what the hey, you only offtopic once.)
The only joy I get watching compiler messages scroll by is laughing my butt off watching all the warnings. Don't these people use lint?
And that's funny only if I'm already in a good mood. Otherwise, I hate having to actually watch the unavoidable visible indicators of the quality of the software I'm about to start using. Just like most people don't like watching sausage being made...from live pigs...
Yeah, I know, if I know so much, why don't I fix it? Because I didn't sign up to indentured servitude, I just want to use the damn software. I realize that violates the canon of Open Source ethics in the minds of the extremists, but I have a job to do and it's not fixing your damn object cast mismatches.
OK, ok, cooling down now.
Thank you, in all sincerity, to the authors of those software packages. Please forgive me if watching 2423 warnings per compile cycle makes me a little crazy.
I don't care for the dependancy model of packages, and I'd much rather install programs myself. That way I know I'm getting the program compiled most efficiently for my computer, and I don't have to worry about dependancy databases
That just means that you'll have to store the dependancy databases in your head. A release of a particular software package, whether it's a package or a tarball of source, depends on other software. Always. "config" goes a long ways towards working that out, but if it doesn't work automagically you're going to have to take it by the hand and lead it to wherever your copy of libfoobar.so.17 might happen to be.
I've just started using yum for RPM management and I'm already liking it a lot. At least dependency management seems a bit cleaner and more automatic.
Hmph. Subvert my paradigm and die a prolonged agonized horrible bloody death.
In this context, there's an incredibly fine line between this and an ATM card skimmer. Particularly if you subvert the paradigm into a portable man-in-the-middle hack attack.
OK, the idea has officially gone from stupid to evil.
Anyway, I wondered (and I have to continue wondering, since the article is/.ed): what's the point? Portable LAN party? One-man mobile tentacle-pr0n provider? Geek chic?
Seriously, without internet connectivity, what's it got? Or are we operating under the delusion that a clutch of wifi afficianados clustering around a self-contained hotspot will spontaneously generate useful, amusing, or at least non-trivial content?
The big loser in this matter may be SCO, said Dion Cornett, an analyst with Decatur Jones Equity Partners LLC, an equity research firm based in Chicago. Having their first publicly announced customer express second thoughts over the deal so soon after its announcement may make it difficult for SCO to sign up other customers, he said.
"For Robert (Marsh) to say that he would not do the deal again, that's certainly going to be heeded by anyone that SCO talks to in the future," Cornett said. (emphasis mine)
I wonder if the EV1 contract has language that prohibits them from publicly disparaging the deal. I wouldn't put it past SCO to demand, among all the rest of the crap, that EV1 continue to publicly play the role of satisfied customer or else. Look out for yet another SCO breach-of-bogus-contract lawsuit!
And I concede that my statement in my grandparent comment is begging to be refuted. ("NO MAJOR OPERATING SYSTEM" is too absolute to stand unchallenged.)
However, I have to ask, which OS (major or minor) are you using?
Also, I have to point out that you aren't claiming protection from buffer overflows, which was the specific context of my original. I understand that many OSs have priv separation, and that's immensely helpful, but protecting against core overruns should be easier. Should be automatic, for God's sake.
And, apparently, buffer overrun protection is still much too rare to allow fair-minded commentators to blame just one OS for permitting a multiplatform application exploit. Which, I maintain, was my point.
A worm or virus on a computer is a computer worm or virus.
A worm or virus on a Microsoft Windows computer is a Microsoft Windows worm or virus.
For crying out loud. What hand-waving are you going to use when the worm arises that compromises a cross-platform software package, like Apache?
"It's a Windows worm that also affect Linux and Unix and MacOS. But mostly a Windows worm. Really"
It serves no purpose but propaganda to shift blame out of the actual compromise layer to the OS, since NO MAJOR OPERATING SYSTEM AVAILABLE PROTECTS AGAINST APPLICATION BUFFER OVERFLOWS.
Thanks, Obvious Obviousington. As I pointed out, I couldn't decide between the two alternatives, so I chose "(c) none of the above" (aka the "Cowboyneal poll option").
Maybe we'll get lucky and someone will mod both of us "-1 Overrated" or "-1 Offtopic". Unless they can't decide between, in case they may post a moderately amusing reply about their dilemma. In which case, you can helpfully point out that they can no longer moderate this thread. ad infinitum.
Slashdot Mirror
It had to be said.
I thought it was the Protoss and the Zerg battling it out on the high seas, to be released in a bundle with Duke Nukem Forever this <whenever>.
Does adding an RF receiver and motors add weight and rigid bulk to the cone, making it more damaging to hit?
It's bad enough if you hit one of the road cones with the battery-powered flashers on the top, but that weighs very little. I hope the folks designing these keep impact-safety factors in mind.
- Outsourcing your attack to overseas cracker groups. Say, the same fine people who keep attacking online betting parlors for extortion. That would make it harder to track down, particularly if they're using zombie-nets.
- What if the hackers ARE the current administration? What's your guarantee that law enforcement will investigate its own bosses? (Or have we already forgotten Watergate?)
If you're caught, you' pretty busted. But the likelihood of being caught aren't astronomically higher than your chances if you futz the old-sk00l election process in the usual time-honored ways.I'm just sayin'.
Your assertion...
which is true.
Not proven. Probably not provable. So all we have is your unsupported assertion. Repeatedly asserting an unproven assertion doesn't constitute proof.
And seeing that a very large portion of the US economy runs on oil, having access to Oil is a good thing from a stratigic point of view.
As an isolated statement, possibly true, but fails to take into account the costs of that access. Both short-term (lives, property, political standing of current administration) and longer-term (strained international relations, future loss of life to terrorism or war subsequent to those strained international relations, the judgement of history).
I'm not arguing that you're wrong. I'm arguing that you don't really know whether you're right, not in any fashion meaningful to anyone else but yourself.
The impression you give with your stance is that you're positive about these beliefs. "Positive" is "wrong" at the top of your lungs.
It'll need a big case, in any event.
Not much of a reach to imagine my WUSB flash pocket drive crashing your WIN XP++ session when I walk into the room. Hell, how are they going to keep this from becoming a wireless DoS attack, crashing systems from afar with tailored WUSB negotiation exploits and high-powered WUSB transmitters? Or will all WUSB drivers be perfect now?
I hereby word-mod you +1 insightful.
Never let principles stand in the way of accomplishing the mission. If the missions calls for Java, render unto Sun what is Sun's and carry on, dammit.
That's an interesting insight. (I don't have mod points, so I'm word-modding. Mod Nazis, bite me.)
The reason mechanical bits sound "wrong" when making high-pitched sounds is that the usual source high-pitch sound in conventional mechanics is friction. Friction sound means lubrication failure, usually followed quickly by breakdown (perhaps at speed, with attendant spontaneous ballistic self-disassembly).
If I understand correctly, the high-frequency components of the "problem" sound of maglevs have absolutely nothing to do with friction. Au contraire, it has to do with frictionlessness (non-contact magnetically-maintained air bearing). So it makes no rational sense that perceived discomfort has anything to do with mechanical breakdown.
But that doesn't mean it's not so. I imagine the reaction to the sound is visceral, not rational, so explaining that "No, it's not breaking down, it always sounds like that" won't help.
There is no Lumber Cartel Black Helicopter Force. Only the Backbone Cabal.
Thank you.
I used to like April Fool's. Now they annoy me like the fools of the other 364.24 days of the year.
And a damn-sight better use for cold-cathode fluorescents than most uber-l33t casemods.
I guess not always. But it seems like it sure should have been in this case, and if the settlement had that loophole then shame on Univention's lawyers for letting that slip.
Another interesting point, too. According to the Groklaw article about the settlement, the per-offense fine is only about 10,000 euros. That's not a lot, really; just a tiny extra bit of marketing budget for the FUD machine. Is that really all the teeth the settlement has?
I'm not sure whether to mod you -2 BSDTroll or +1 BSDFunny. However, I'll comment instead. (Commented earlier downthread, so it's already a foregone decision, but what the hey, you only offtopic once.)
The only joy I get watching compiler messages scroll by is laughing my butt off watching all the warnings. Don't these people use lint?
And that's funny only if I'm already in a good mood. Otherwise, I hate having to actually watch the unavoidable visible indicators of the quality of the software I'm about to start using. Just like most people don't like watching sausage being made...from live pigs...
Yeah, I know, if I know so much, why don't I fix it? Because I didn't sign up to indentured servitude, I just want to use the damn software. I realize that violates the canon of Open Source ethics in the minds of the extremists, but I have a job to do and it's not fixing your damn object cast mismatches.
OK, ok, cooling down now.
Thank you, in all sincerity, to the authors of those software packages. Please forgive me if watching 2423 warnings per compile cycle makes me a little crazy.
And that's why it was the best summer ever!
That just means that you'll have to store the dependancy databases in your head. A release of a particular software package, whether it's a package or a tarball of source, depends on other software. Always. "config" goes a long ways towards working that out, but if it doesn't work automagically you're going to have to take it by the hand and lead it to wherever your copy of libfoobar.so.17 might happen to be.
I've just started using yum for RPM management and I'm already liking it a lot. At least dependency management seems a bit cleaner and more automatic.
In this context, there's an incredibly fine line between this and an ATM card skimmer. Particularly if you subvert the paradigm into a portable man-in-the-middle hack attack.
OK, the idea has officially gone from stupid to evil.
Anyway, I wondered (and I have to continue wondering, since the article is /.ed): what's the point? Portable LAN party? One-man mobile tentacle-pr0n provider? Geek chic?
Seriously, without internet connectivity, what's it got? Or are we operating under the delusion that a clutch of wifi afficianados clustering around a self-contained hotspot will spontaneously generate useful, amusing, or at least non-trivial content?
I don't get it.
The big loser in this matter may be SCO, said Dion Cornett, an analyst with Decatur Jones Equity Partners LLC, an equity research firm based in Chicago. Having their first publicly announced customer express second thoughts over the deal so soon after its announcement may make it difficult for SCO to sign up other customers, he said.
"For Robert (Marsh) to say that he would not do the deal again, that's certainly going to be heeded by anyone that SCO talks to in the future," Cornett said.
(emphasis mine)
I wonder if the EV1 contract has language that prohibits them from publicly disparaging the deal. I wouldn't put it past SCO to demand, among all the rest of the crap, that EV1 continue to publicly play the role of satisfied customer or else. Look out for yet another SCO breach-of-bogus-contract lawsuit!
Yours is to be an example of what not to do, and why not to do it.
However, I have to ask, which OS (major or minor) are you using?
Also, I have to point out that you aren't claiming protection from buffer overflows, which was the specific context of my original. I understand that many OSs have priv separation, and that's immensely helpful, but protecting against core overruns should be easier. Should be automatic, for God's sake.
And, apparently, buffer overrun protection is still much too rare to allow fair-minded commentators to blame just one OS for permitting a multiplatform application exploit. Which, I maintain, was my point.
A worm or virus on a Microsoft Windows computer is a Microsoft Windows worm or virus.
For crying out loud. What hand-waving are you going to use when the worm arises that compromises a cross-platform software package, like Apache?
"It's a Windows worm that also affect Linux and Unix and MacOS. But mostly a Windows worm. Really"
It serves no purpose but propaganda to shift blame out of the actual compromise layer to the OS, since NO MAJOR OPERATING SYSTEM AVAILABLE PROTECTS AGAINST APPLICATION BUFFER OVERFLOWS.
Maybe we'll get lucky and someone will mod both of us "-1 Overrated" or "-1 Offtopic". Unless they can't decide between, in case they may post a moderately amusing reply about their dilemma. In which case, you can helpfully point out that they can no longer moderate this thread. ad infinitum.
After all, it's funny because it's true. Bet on it.
Oh, well.
I was going to do the "grassy knoll" joke, you insensitive clod!