News for hackers. Stuff that matters.
Re:The Emacs Lock-In Effect or the Emacs Sunk Cost Fallacy by _huayra_ on Friday August 06, 2021 @10:43PM (#28095230)
> 1. A good concurrency model.

This is definitely the biggest pain point, especially as people go to expand their use of Emacs (e.g. with Doom, adding more modules and integrations, one has to be careful to lazily evaluate config blocks to avoid loading everything at startup).

Even without such extensive configs, working on a large repo with a slow I/O (e.g. some network mount) with magit will cause large pauses once a command finishes if it has to refresh the magit buffer, or trying to search myriad org agenda files for an ID or text search (e.g. org rifle) will basically lock up emacs.

I do at least look forward to Emacs 28, which iirc is going to get native-comp (although that is already available as an experimental branch perhaps?).

Re:The Emacs Lock-In Effect or the Emacs Sunk Cost Fallacy by b3morales on Saturday August 07, 2021 @02:14PM (#28100647)
Native comp was merged to the mainline a few months ago. It's behind a config flag `--with-native-compilation`. There is not yet an official release that includes it, but it's fairly common for people to run Emacs built from the mainline source.
Re:The Emacs Lock-In Effect or the Emacs Sunk Cost Fallacy by githubalphapapa on Wednesday August 11, 2021 @03:03AM (#28138945)
> trying to search myriad org agenda files for an ID or text search (e.g. org rifle) will basically lock up emacs.

Please try `org-ql` and `helm-org-ql`; these newer search tools perform better than `org-rifle` and generally supersede it.