kdevelop (Re: Proposal to plan for "Milestone Releases" on the way to KDE4)

Alexander Neundorf neundorf at kde.org
Fri Jan 27 19:14:11 GMT 2006

On Friday 27 January 2006 19:19, Guillaume Laurent wrote:
> Alexander Neundorf wrote:
> > On Friday 27 January 2006 06:18, Waldo Bastian wrote:
> > ...
> >
> >> Another option is to make Eclipse work really well for KDE development.
> >
> > I do prefer kdevelop over it, compared to eclipse it's lean and mean and
> > snappy. Eclipse is slow and cosumes huge amounts of memory. Probably
> > simply because it's java.
> No, it's mostly because it indexes a sh*tload of stuff for completion
> and browsing. 

It's also slow with these functions disabled. Enabling them makes it unusable 
(on a 2 GHz CPU with 512 MB RAM).

> Yes, eclipse requires a >2Ghz CPU and 1Gb of RAM to work
> comfortably. But unless your time is worth nothing, that's a cheap
> investment to make with a huge profit in return.

Once upon a time people claimed that windows is slow and huge and bloated, and 
nowadays open source software requires a CPU > 2 GHz and at least 1 GB RAM to 
(basically) edit some text files ?

(slightly exaggerated, but still IMO unacceptable).

Two of my colleagues (both have 2 GHz Intel, 512 MB RAM) use it work. MSVC 
opens almost instantly, Eclipse takes a lot of time to start (I didn't 
measure, but it must be around 20..40 seconds), and also a lot of time to 
swap back in when not used for some time (on windows). KDevelop OTOH is 
usable on a PIII 450 MHz and 256 MB RAM.

Work: alexander.neundorf AT jenoptik.com - http://www.jenoptik-los.de
Home: neundorf AT kde.org                - http://www.kde.org
      alex AT neundorf.net               - http://www.neundorf.net

More information about the kde-core-devel mailing list