in reply to Re^2: Shared libraries^Wmodules in Perl
in thread Shared libraries^Wmodules in Perl

Wow. Yet another reason to completely avoid Java altogether. Just the security issues alone make this undesirable, let alone the synchronization, the memory dirtying, and the potential for deadlocking.

Yes, I understand that this is only supported for a certain set of modules, presumably ones that have been "vetted" by some authoritative group. All this means is that there's another entry to hack Java applications by replacing one of these libraries with a nefarious version. And, before you say "That can't happen", the people who designed Windows weren't stupid ...


My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
  • Comment on Re^3: Shared libraries^Wmodules in Perl

Replies are listed 'Best First'.
Re^4: Shared libraries^Wmodules in Perl
by zentara (Cardinal) on Sep 13, 2005 at 10:38 UTC
    Wow. Yet another reason to completely avoid Java altogether.

    You are right there. I was running a java based tv guide program called "freeguide" and it took a whopping 276 megs of virtual memory. I'm working up a Tk version to replace it.


    I'm not really a human, but I play one on earth. flash japh