On Tuesday 25 April 2006 04:47, Michal vorner Vaner wrote: > Anyway, GPG was designed to run under UNIX systems, where launching a > binary is really fast (it has to be, since many good application use > external programs for different actions, which menas configurability and > not duplexing of code) and then it was ported to windows. Windows is not > the main target platform for this, as I guess. (It is used from > commandline, for example, which is quite a problem there)
It took this long for the true reason to appear in the thread -- Windows is
slow at forking (actually it doesn't "fork" as such) new processes, while
practically every other OS is fast. This is why Windows doesn't have the
mentality of using existing executables to perform tasks, but uses DLLs
instead.
One might say that the correct mentality for porting to Windows is to provide
a DLL to eliminate startup costs, but unfortunately that's going to take
someone's time, and most people would spend less time migrating to an OS that
doesn't suck, than would be spent changing something like GnuPG to work as a
shared library.
TX
--
Email: [EMAIL PROTECTED]
Jabber ID: [EMAIL PROTECTED]
Web site: http://trypticon.org/
GPG Fingerprint: 9EEB 97D7 8F7B 7977 F39F A62C B8C7 BC8B 037E EA73
pgpNKyRPcQUWK.pgp
Description: PGP signature
