Slashdot Mirror


User: PirateDuck

PirateDuck's activity in the archive.

Stories
0
Comments
4
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 4

  1. Re:Why Hype 2.0 Doesn't Matter on Five Reasons Why Web 2.0 Matters · · Score: 0
    You don't have any idea what your talking about. Web 2.0 is poised to expedite e-business platforms and mesh sticky supply-chains with integrated transparent interfaces that transform visionary markets. Through iterating one-to-one paradigms, it revolutionize cross-media mindshare.

    I would like to invest in your company -- please tell me where I should send the money. Don't worry about sending me stock certificates, they'll be worthless come Crash 2.0 anyway.

    --
    Pirate Duck
    AnagramLogic Anagram Finder

  2. FTL surgery on Robots Might Allow For Space Surgery · · Score: 0, Redundant
    Delays in communication because of the distance to space would mean surgeons on earth would have tell astronauts what commands to give the robots

    Because, you know, surgeon -> astronaut -> robot is much faster than surgeon -> robot.

  3. Goodbye free beer! on BBC Commentator Goes After Software Licensing · · Score: 1
    The author of this article doesn't seem to get how the market works. Adding costs to the producers of software makes the cost of that software go up for the end user, and liability is definitely a cost. For-profit software gets more expensive, and so does free software. Making it not free. Once Linus and the rest of the kernel krew got sued out of existance, who would be willing to step into their place?

    Open source probably wouldn't die, since one could still have software that's free as in speech that happens to not be free as in beer, but it would be hit hard. Linux and Apache would survive. Mozilla/Firefox? Not so much...

  4. Re:It happened where I used to work on Reducing The Negative Impact of Laptops · · Score: 1

    Somewhat the reverse of this happened at a large corporation where I was teaching a security class. We set up an unsecured laptop as part of a lab to give the students some hands on security testing experience, and during a break the lab network was bridged to the corporate network to allow people to check email. Class starts up again, and one of the instructors notices that the test laptop was infected with nimda... erk!

    Not really what we had in mind, but it worked out ok: we were able to inform their IT staff of an infected machine on their corporate network and provide an IP, and the local IT folk got to pick up the phone and call the main office and nonchalantly ask "so... you folks already know about your infected machine, yes? No? Oh my! Well...". It wound up being a nice object lesson for the class, we just needed to re-image the laptop and, um, be a bit more careful about where it got plugged in...