Subject: Re: plugin loading
From: Rui Miguel Seabra (firstname.lastname@example.org)
Date: Thu Oct 25 2001 - 09:00:11 CDT
On Thu, 2001-10-25 at 14:57, Dom Lachowicz wrote:
> > Arguments: 1) Performance. <argument> plugin loading time will be half
> > the startup time</argument> <response> time to load any real-world
> > plugin is negligible, microscopic. and there aren't even that many
> > plugins that you can put in your plugin dir. Also, each distro or
> > branch-distro has its own target audience (win9+->Pent, elks->286, etc)
> > so they can choose what is reasonable to include.</response>
> Completely correct. It might make more sense to ship a DOC reader plugin on
> Win32 and not on Linux, or at least have a check-box in an installer
> "intelligently" defaulted based on the user's system. Plugin loading time is
> negligable, and startup time is typically a *minute* fraction of total running
> time. Abi already loads faster than emacs and almost as fast as vi on Linux.
> That's fscking fast for a word-processor (or anything, for that matter), and
> plugins aren't likely to put much of a dent into our startup performance.
I tend to disagree with this behaviour, unless it was an hypotethical
A ms word .doc reader will definetly be a must have on a default abi
installation, whichever platform there is. Maybe less so in windows than
other platforms where ms word is not available, and many feel the need
to be able to read the document.
Other than that, on my 500mhz machine, abiword takes more or less
between 2 to 3 seconds loading, and vi is almost instantaneous.
-- + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Ghandi + So let's do it...?
This archive was generated by hypermail 2b25 : Thu Oct 25 2001 - 09:04:11 CDT