Replies to ceruleansparkold, page 54

  1. @ceruleanspark I don't got no time to play around, what is this?

    Wednesday, 12-Jun-13 18:50:45 UTC from web in context
  2. @ceruleanspark The same thing as what happens when a toad is struck by lightning.

    Wednesday, 12-Jun-13 18:45:54 UTC from web in context
  3. @ceruleanspark It times out and crashes with an error message saying that you done broke the internets

    Wednesday, 12-Jun-13 18:25:57 UTC from MuSTArDroid in context
  4. @ceruleanspark Buh.

    Wednesday, 12-Jun-13 18:24:55 UTC from web in context
  5. @ceruleanspark Explosions?

    Wednesday, 12-Jun-13 18:22:10 UTC from web in context
  6. @ceruleanspark I'll trade ya

    Wednesday, 12-Jun-13 18:15:51 UTC from web in context
  7. @ceruleanspark Ketchup.

    Wednesday, 12-Jun-13 18:14:45 UTC from web in context
  8. @ceruleanspark Baked beans.

    Wednesday, 12-Jun-13 18:13:49 UTC from web in context
  9. @ceruleanspark Ah well then, I take it that's a good result

    Wednesday, 12-Jun-13 15:51:35 UTC from web in context
  10. @ceruleanspark So better then now I take it?

    Wednesday, 12-Jun-13 15:34:13 UTC from web in context
  11. @ceruleanspark Well, trial and error are best of friends

    Wednesday, 12-Jun-13 14:32:55 UTC from web in context
  12. @ceruleanspark Hahaha, oh my. This'll be the best learning experience ever! >post vanishes >forgets to do it

    Wednesday, 12-Jun-13 14:15:59 UTC from web in context
  13. @ceruleanspark Well now, that's never going to end well, but that's the idea behind trying these things isn't it. Learn how to work them

    Wednesday, 12-Jun-13 13:50:14 UTC from web in context
  14. @ceruleanspark Indeed it will

    Wednesday, 12-Jun-13 13:44:33 UTC from web in context
  15. @ceruleanspark Sounds to me like it'd be better to designate which part of the cluster deals with what, making sure that they sync in the right timings

    Wednesday, 12-Jun-13 12:54:21 UTC from web in context
  16. @ceruleanspark yup... :/ ohh well

    Wednesday, 12-Jun-13 12:38:05 UTC from web in context
  17. @ceruleanspark Did you say "nerd"?

    Wednesday, 12-Jun-13 10:44:21 UTC from web in context
  18. @ceruleanspark Always

    Wednesday, 12-Jun-13 10:32:33 UTC from web in context
  19. @ceruleanspark YOU WILL BREAK IT

    Wednesday, 12-Jun-13 10:06:09 UTC from web in context
  20. @ceruleanspark rip serrio.

    Wednesday, 12-Jun-13 08:48:09 UTC from web in context
  21. @ceruleanspark Getting funky

    Wednesday, 12-Jun-13 07:52:06 UTC from web in context
  22. @ceruleanspark You would kill everything that moves with three MySQL servers? We would kill everything that moves with ONE MySQL server.

    Wednesday, 12-Jun-13 07:49:47 UTC from web in context
  23. @ceruleanspark IF you can pick them up!

    Wednesday, 12-Jun-13 07:49:45 UTC from web in context
  24. @ceruleanspark Four, NUKE THAT SOME *****

    Wednesday, 12-Jun-13 07:49:44 UTC from web in context
  25. @ceruleanspark I see what you did there. MGS reference #

    Wednesday, 12-Jun-13 07:48:49 UTC from web in context
  26. @ceruleanspark Oh good god

    Wednesday, 12-Jun-13 07:46:32 UTC from web in context
  27. @ceruleanspark Kaboom

    Wednesday, 12-Jun-13 06:48:05 UTC from web in context
  28. @ceruleanspark "I don't want to set the world on fire"

    Wednesday, 12-Jun-13 06:34:12 UTC from web in context
  29. @ceruleanspark I won't try to defend anything or praise anything. I'll just see where the cards lay when the consoles drop.

    Wednesday, 12-Jun-13 06:17:53 UTC from web in context
  30. @ceruleanspark yeah....maybe not the best marketing strategy. But you know if the console winds up being as "future-proof" as they are claiming we could be eating our words some day.

    Wednesday, 12-Jun-13 06:10:31 UTC from web in context