Slashdot Mirror


User: mkavanagh2

mkavanagh2's activity in the archive.

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

Comments · 103

  1. Re:True? on Company Claims Development of True AI · · Score: 1

    imagine a beowulf cluster of these things

    Hot grits.

  2. Re:True AI on Company Claims Development of True AI · · Score: 1

    More likely you'll read about it in Janes' 10 years before it happens.

  3. Re:I'm sorry, but who? on Libranet On The Rocks · · Score: -1, Flamebait

    You can't fucking read.

  4. Perl comes with an obfuscator by default.. on 'Protecting' Perl Code? · · Score: 5, Funny

    ..and it's called "Perl". You don't need to do anything at all for your code to be unreadable.

  5. let's count up the score on How to Go About Team Building? · · Score: 4, Insightful
    • vaporware project
    • placeholder homepage
    • bizarre aspirations to be linus torvalds
    • discounting a good answer for frivolous reasons
    • crap question


    result: another awesome ASK SLASHDOT. As they say in Enemy Territory:
    v56
  6. Re:Good plan, old design on NASA Scraps Shuttle And Returns to Rockets · · Score: 1

    NASA isn't a company. :)

  7. oh slashdot, you card on Dreadnought Demos Released · · Score: 4, Informative

    This isn't an upcoming FPS. This is a tech demo for Torc's game engine and AMD's AWESOME64(TM) processors.

  8. Re:What I would do... on DirectNIC Crisis Manager Braves the Chaos of New Orleans · · Score: 1

    Canadian and Mexican? If you think that'll help, go ahead. British? Yeah, sure, if you don't mind the fact that it'll take a month to mobilise any significant force across the Atlantic. That's not a dig at the Royal Navy in any way; I just think you've forgotten that Britain isn't an island in the Caribbean.

    As for the "Fuck Iraq" bit, fuck you.

  9. Repeat ad nauseum on Where New Tech Should Libraries Try Next? · · Score: 1

    Books.

  10. Re:Why the space shuttle? on It isn't Easy Being Green and Getting to LEO · · Score: 1

    And, of course, I'm sure your car burns pure hydrogen in pure oxygen, producing only water, as with the Space Shuttle Main Engine.

  11. Re:It's a Mature game +18 why warn parents? on GTA Sex Game Debate Intensifies · · Score: 1

    intertron

  12. Re:Outsourced ?. on Layoffs at OSDL · · Score: 1
    Then come back here again and explain to us how exactly OSDN opening an office in darkest India would be a good thing.


    Because you're one of those awesomely smart Aryan ubermensch, you typoed "OSDL", who employ Linus Torvalds, to "OSDN", who employ CowboyNeal.

    Smrt!
  13. Re:What the cunting fuck. on Google Accelerator: Be Careful Where You Browse · · Score: 1

    do yuo like to fuck your own ass with your tongue :@

    lol fag :@

  14. Re:What the cunting fuck. on Google Accelerator: Be Careful Where You Browse · · Score: 1

    And I'm saying that Google are still culpable for this. They have a responsibility to be aware about the environment they are releasing their software into, and they did not think for a second before putting out software that fucks up severely with the pre-existing state of affairs.

    It doesn't matter two stone shits that the existing state of affairs is in breach of the specs; if Google released a webbrowser that wrote pseudo-random 1s and 0s to the entire harddrive several times over whenever it encountered invalid HTML (oh no! the specs!), it would be Google's fault. And it's Google's fault now.

  15. Re:What the cunting fuck. on Google Accelerator: Be Careful Where You Browse · · Score: 1

    You didn't do this rite, get out :@

  16. Re:What the cunting fuck. on Google Accelerator: Be Careful Where You Browse · · Score: 1

    You're not going anywhere. I have not suggested that the people who wrote these sites were not breaking the specs. I have suggested, for it is so, that it is Google's fault when Google's software interoperates badly with such sites, because Google have a responsibility to be aware.

    Incidentally, you're a retard and I am burning karma so fuck you. :@

  17. Re:What the cunting fuck. on Google Accelerator: Be Careful Where You Browse · · Score: 0, Flamebait

    You're really smart and I love you, please have my babies and I want you to lead the country because you are a smart guy and fair and just, did I mention you are smart :)

  18. Re:What the cunting fuck. on Google Accelerator: Be Careful Where You Browse · · Score: 1

    False analogy.

    A correct analogy: A train track goes unused for many years. Despite warnings, it becomes a popular playing area for children, due to the surrounding trees, the open space, and the interesting terrain. Everyone is aware that hundreds of children play on the disused track every day.

    One day, some cunt runs a high speed service down the track and kills 50 kids. Whose fault is it?

  19. Re:What the cunting fuck. on Google Accelerator: Be Careful Where You Browse · · Score: 1

    I wouldn't be so harsh if this was some guy releasing stuff on a random .org domain that three people visit in a year. This is Google we are talking about. They should be well aware that even public betas will be used by people as if they are the greatest software ever created, oh hallelujah, we thankyou for this software we are about to recieve, our lord and master Google, forever and ever amen.

    They screwed up and I hope everyone remembers this for a while. They had better not screw up like this again, and they had better issue a prominent apology.

  20. google got hacked on Google Accelerator: Be Careful Where You Browse · · Score: 1

    hey guys did i do this rite

  21. Re:What the cunting fuck. on Google Accelerator: Be Careful Where You Browse · · Score: 2, Insightful

    It is still Google's fault. Any half-competent software engineer would have thought about this, and the people at Google did not. It doesn't matter if the websites affected were non compliant to the RFC, because they were the existing state of affairs. Google stuck this crap out there with no thought for the existing state of affairs, so it is their fault. It's the practical view of things, and the practical view is the only one that anyone should take.

  22. Re:Stupid web developers on Google Accelerator: Be Careful Where You Browse · · Score: 0, Troll

    I hope you and your parent post die from some form of catastrophic genital haemorrhage.

  23. Re:What the cunting fuck. on Google Accelerator: Be Careful Where You Browse · · Score: 3, Funny

    Oh, and obligatory "lol slashdot" comment: Think about what most people would be saying if Internet Explorer suddenly did this because Microsoft thought it would be a good idea. You'd be all over them like rats over a rotting horse cock.

  24. What the cunting fuck. on Google Accelerator: Be Careful Where You Browse · · Score: -1, Flamebait

    Hey, shitfuck: it's obviously Google's fault. Web application designers are dumb for using GET for stuff like this, but it was not a real problem for users until the stupid fucks at Google decided to release something awful like GWA without thinking for a second of the responsibility that should come with the high profile of Google. It was people at Google that were too arrogant to think about what they were doing, and it is the fault of people at Google.

  25. Re:Obelisk of Light on Total Annihilation Remake Released · · Score: 1

    All glory to the obelisk of light, but I forgot it because the rest of Red Alert vastly outshines the original C*C.

    Massive amphibious landings?

    A hundred Yaks converging on the ememy construction yard, spraying bullets till the ground crunches with lead underfoot, then retreating from whence they came?

    Huge fleets supported by cruisers?

    A tesla-flanked heavily mined gauntlet of death for a famous last stand?

    Just for the quirkyness, breaking down a few trees to form an unexpected attack route?

    Nuclear missiles?

    All of the above?

    Hell yes.