1. 18
  1.  

  2. 5

    It seems their CEO is still working in the industry:

    https://www.linkedin.com/in/rainer-poertner-37bb9511/

    Granted that I’d hate to be judged today by many of my own actions in the 90s - 20+ years is a long time, and he may well be a changed man.

    But it seems odd to me that going public with a tech company built on outright fraud didn’t entirely derail his career.

    1. 2

      RAMDoubler on the Mac actually worked, however. It was a very clever idea.

      1. 4

        It does, but it has an “advantage”: classic MacOS memory allocation is dreadfully inefficient, essentially unchanged from the old MultiFinder where allocations were generally fixed and grabbed more than they might initially need because they might not be able to get it again. (There was eventually support for temporary memory, essentially a system heap allocation, but this has important limitations and wasn’t frequently used.) Combine that with people’s tendencies to increase those allocations further in Get Info so applications wouldn’t get unstable (goodness knows I did this myself all the time), and you potentially have a lot of unused memory sitting around at any given time that RAM Doubler could just steal, even from the Finder. No compression necessary. When this pool was exhausted, RD thrashed as bad as anything else trying to compress paged-out memory.

        RD was magical when it worked, and it’s essential on machines with pathetic RAM ceilings like the 1400. But it worked as well as it did at memory management largely because the classic MacOS was so bad at it.