Slashdot Mirror


User: bartash

bartash's activity in the archive.

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

Comments · 105

  1. This allows homograph attacks on RIPE NCC Responds to ICANN CEO's Proposal · · Score: 1

    See Inside risks: The homograph attack
    CACM vol 45 issue 2 (Feb 2002)
    http://doi.acm.org/10.1145/503124.503156

  2. Eclipse is IBM's answer to NetBeans on IBM Launches Public Domain Project "Eclipse" · · Score: 1

    NetBeans is an OS project that does the same sorts of things as eclipse. It is written in Java and allows extensions to the IDE through a plugin mechanism.

    Information at http://www.netbeans.org

    NetBeans is the basis for Sun's Forte for Java.

    Information at http://www.sun.com/forte/

  3. Worms known before 1988 on Don't Forget That Worms Happen Everywhere · · Score: 1
    Works were known about before Morris unleashed his. I used to work on a project that had worms as a programming model.

    A program in Equus was a constructive variety of "worm" program that sought out computing resources and adapted to changing environments.

    See

    T. Kindberg, A.V. Sahiner and Y. Paker (1987). Worm Programs, Distributed Operating Systems, Theory and Practice, Y. Paker, J-P. Banatre and M. Bozyigit, eds., NATO ASI Series F, vol. 28, 1987, pp. 335-379.

    or

    Equus: an Environment for Reconfigurable Distributed Computations, Tech. Report no. 591, Queen Mary & Westfield College Dept. of CS, 1992.

  4. First Computer as we know it was the Manchester on Happy 50th Birthday, UNIVAC 1 · · Score: 1

    The first stored program digital computer was the Manchester Mark I. Before this computers had their programs controlled through switches or other weird mechanisms. Of course becuase the inventors were not American this is often ignored. Just like TV, which was really invented by a Scot

  5. My favourite bit: on Microsoft Releases C# Language Reference · · Score: 1

    C# provides the ability to write "unsafe" code. Such code can deal
    directly with pointer types, and fix objects to temporarily prevent the
    garbage collector from moving them. This "unsafe" code feature is in
    fact a "safe" feature from the perspective of both developers and users.
    Unsafe code must be clearly marked in the code with the modifier unsafe,
    so developers can't possibly use unsafe features accidentally, and the
    compiler and the execution engine work together to ensure that unsafe
    code cannot masquerade as safe code.