Re: Time to heat up the new module discussion



Ben Maurer wrote:

> Please read my previous emails. Designing everything in C will not help.
> Evolution, OpenOffice and Firefox are evidence that writing your app in
> C does not make it memory efficient. In the long term, a moving GC may
> be beneficial.

Does "using a GC" really mean you have to use a big bloated
memory-hungry virtual machine ? Well, no. Inkscape uses a GC, and it is
written in C++. D should provide a GC while not resting on a VM.

If ever VM were able to share libs, it would be a great improvement, but
currently they can't. It means the managed part of the code is loaded
for every managed app you launch. Which is far from optimal in the case
of permanently running apps.

As I said, I don't care about apps that don't stay alive in background.

> At some point, we also have to realize that users with less memory do
> need to make compermises. For example, such a user might want to choose
> not to use Beagle.

I don't use Beagle, and in fact I hope the alternate Tracker project
will solve this problem. I don't use deskbar as well, nor banshee since
the player is at the limit between a daemon and a classical app. But I
can assure you I use python apps and even C# ones.




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]