[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs Lisp's future
From: |
David Kastrup |
Subject: |
Re: Emacs Lisp's future |
Date: |
Wed, 17 Sep 2014 16:30:44 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux) |
Eli Zaretskii <address@hidden> writes:
> You are wrong here. Emacs 23 added many CPU-intensive features, like
> visual-line-mode. Emacs 24 added bidirectional display, which makes
> redisplay need roughly twice as much juice as Emacs 23 needed. And
> these are only two examples that pop up in my head after a 3-sec
> thought; I'm sure there are more.
>
> So it's not like we use up every additional CPU cycle the chips are
> giving us, but we are certainly using significantly more than we did
> 10 years ago.
One of the most costly changes was post 20.2 (?) when buffer and string
positions became expressed as character offsets rather than byte
offsets.
--
David Kastrup
- Re: Emacs Lisp's future, (continued)
Re: Emacs Lisp's future, Phillip Lord, 2014/09/17
- Re: Emacs Lisp's future, Nic Ferrier, 2014/09/17
- Re: Emacs Lisp's future, Stefan Monnier, 2014/09/17
- Re: Emacs Lisp's future, Phillip Lord, 2014/09/17
- Re: Emacs Lisp's future, Eli Zaretskii, 2014/09/17
- Re: Emacs Lisp's future,
David Kastrup <=
- Re: Emacs Lisp's future, Eli Zaretskii, 2014/09/17
Re: Emacs Lisp's future, Phillip Lord, 2014/09/17
performance isn't a concern in ... Emacs Lisp's future, Nic Ferrier, 2014/09/17
Re: performance isn't a concern in ... Emacs Lisp's future, David Kastrup, 2014/09/17
Re: Emacs Lisp's future, Thorsten Jolitz, 2014/09/18
Re: Emacs Lisp's future, Stefan Monnier, 2014/09/17
Re: Emacs Lisp's future, Taylan Ulrich Bayirli/Kammer, 2014/09/17
Re: Emacs Lisp's future, David Kastrup, 2014/09/17
Re: Emacs Lisp's future, Taylan Ulrich Bayirli/Kammer, 2014/09/17
Re: Emacs Lisp's future, Daniel Colascione, 2014/09/17