On 12/08/2011 16:16, Graeme Geldenhuys wrote:
But as I also list, opening 208 units, the speed in MSEide is near
instant compared to Lazarus IDE (any version of Lazarus, old or new).
15 secs for 200 units are NOT a bad time. And btw, older lazarus was
slower, there was recent work.
Part of this time (and very minor amount of memory 100kb for every
25.000 (actually I believe 100kb for every 50.000) lines, go into
functionality that is broken in MSEide.
Try horizentol scroll in MSE with lines longer than (afaik) 2000 chars.
Yes, maybe not really needed to edit pascal code. But an editor should
be able to deal with that.
Another bit of time is used by codetools. MSEide doesn't have them. It
is every users choice to decide if they need them, and then to use
MSEide or Lazarus.
I haven't compared the highlighter for pascal. But it may be similar.
that use the memory. but memory is rather cheap nowadays?
So that's your answer. There is no issue even though memory usage double
between each release?
IMHO, this is a simplified view. And also remember 0.9.30 was a big
release, after a long time...
Without knowing where this memory went, there is no telling how memory
usage will look in future. It may well be, that some big amount went
into a feature, that is well worth it, and that is of a kind that one
can be sure, it will not happen with every release.
I am not having the time now to look into it.
But certain functionality, comes at certain cost. Lazarus priors the
functionality over the cost (that does not mean Lazarus ignores the
cost, but it accept certain costs, for certain features). you can choose
to use it or not.
I am certain that if you can find ways to save that memory, without
cutting functionality, then this will not be disregarded (It doesn't
mean it will be accepted immediately, and without feedback or
adaptations required....)
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
