News for hackers. Stuff that matters.

A comment on Bad NEWS, Emacs. Parent comment

Re:Bad NEWS, Emacs by janice1999 on Sunday December 10, 2023 @09:48AM (#38591843)
I disagree. As a developer I think breaking literally decades old workflows for users without notice or any level of concern is a bad thing. For a program with users so reliant on muscle memory, I think the impact is far worse.
[ Parent | on HN ]
Re:Bad NEWS, Emacs by smitty1e on Sunday December 10, 2023 @10:02AM (#38591932)
The friction seemed less about the change as such as in the unilateral delivery.

Even good change (whether or not this is) needs a gentle transition.

[ Parent | on HN ]
Re:Bad NEWS, Emacs by jonathanstrange on Sunday December 10, 2023 @10:16AM (#38592047)
If I understood this correctly, the new behavior cannot be customized back to the old behavior. If that's true, then that's obviously very bad. Generally, as an Emacs user, I don't just want an opt-in or a gentle transition, I need to be able to customize everything to my needs.
[ Parent | on HN ]
Re:Bad NEWS, Emacs by smitty1e on Sunday December 10, 2023 @01:10PM (#38593491)
This is Emacs, so one presumes that it's a SMOeL (Simple Matter Of eLisp) problem.

However, it seems tasteless to impose the burden.

[ Parent | on HN ]