Re: Imports / inclusion of s.el into Emacs

[Eli Zaretskii]

> Cc: address@hidden, address@hidden, address@hidden,
>  address@hidden, address@hidden
> From: Dmitry Gutov <address@hidden>
> Date: Mon, 4 May 2020 21:44:58 +0300
> 
> > The reaction to this "little change" could have fooled me.
> 
> In your opinion at the time it was little, IIRC. One of the reasons it 
> got in, I guess.

No, I didn't think it was little.

> >> Second, there were no noticeable consensus, inside or outside the
> >> core, that the new behavior is better
> > 
> > Not true.  There was complete consensus among those who discussed the
> > feature before it went into implementation.
> 
> Among the 2-3 people who participated in the highly technical 
> bug-report/discussion about the display engine? Please be serious. That 
> doesn't reflect the opinions even across emacs-devel, much less the 
> community at large.

Those were all the people who participated in the discussion.
Everyone who cared.

> And once we found out the backward compatibility problem, and all the 
> associated details, there was still one solution available: revert. 
> That's what we usually do when we don't manage to fix a regression 
> before a release, don't we?

Except that wasn't a regression.

> > So what is the lesson you suggest to take out of this example, in the
> > context of "adapting"?
> 
> Maybe that backward compatibility is not as important as some people 
> like to claim? Other lessons would be less kind to type out.
> 
> In any case, I don't see that particular change affecting the experience 
> of new Emacs users much one way or another (as long as all the themes 
> work). Thus it's not a great example of Emacs "adapting" to contemporary 
> user expectations.

Then I'm sorry to say it, but you have learned nothing from that
event.  Nothing useful, anyway.  Too bad.