Slashdot Mirror


User: GalenBB

GalenBB's activity in the archive.

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

Comments · 6

  1. How quantum computing *really* works on Y Combinator-Funded Startup To Do Quantum Computing -- Only Better (bizjournals.com) · · Score: 1

    Here's how quantum computing really works:

    It splits reality into millions of possible universes, trying a different answer in each one. Then it uses quantum interference to destroy every universe where the answer comes out wrong. When it's done, you know the answer you have is right.

  2. Who really owns the specification? on Our Attorney's Response To Microsoft · · Score: 1
    Actually, the document in question is a derivative work of the original Kerberos specification by some good people at MIT. Technically, it can be argued that MIT owns the copyright on the document in question; and they have allowed unlimited redistribution rights.

    IANAL, but I've heard worse arguments from Microsoft. Besides, this is the same argument that has shut down Star Wars sites and many others.

  3. Re:Why they went under: on Goodbye, Number Nine · · Score: 1
    Search for: Linux

    Sorry, but search returned no results.

    Try http://www.nine.com/support/docs/linux.html

  4. Re:Well, they did make a BIG mistake w/ Linux driv on Goodbye, Number Nine · · Score: 1

    Huh??? Number Nine has supported Linux, either directly or indirectly, since around 1993. I personally was responsible for much of this activity, and Perl was not a part of it.

  5. Slashdot EULA on Microsoft Asks Slashdot To Remove Readers' Posts · · Score: 1
    By clicking on "Read More", you hereby give up your rights under the DMCA to request the removal of any replies to this article.

  6. Re:Internet's Scalability on ICMP_HOST_BELOW_HORIZON - TCP/IP Into Orbit · · Score: 1
    Vinge's books are great, but they have little relevance to the question at hand; he assumes messages can travel faster than light under certain circumstances. The real world isn't like this, no matter how much you want it to be.

    The real question becomes: "How do we extend internet protocols to handle ping latencies ranging anywhere from seconds to centuries?" The new protocols should have redundant transmissions and *very* large buffer caches. Timeouts shouldn't occur until some multiple of the latency has passed.

    Programs using these protocols should try to anticipate demand and pre-send as much data as possible. For huge distances, it might just be better to send a complete backup regularly until told it isn't necessary anymore.

    Another thing worth noting is that these protocols will be relatively immune to the "embrace, extend, extinguish" attacks we all know and love because of the amount of time it will take to update the entire network.