Why should I use Remacs?

[marcbowes]

Hi,

This seems like a cool project and the README does a great job of communicating the rationale. The thing that's not clear (yet?) is the end-user benefit. Hopefully along the way there will be bugfixes, security fixes or performance improvements. Maybe even some distinct features (e.g. improvements around concurrency)? Having a section, e.g. in the README, about why users should make the switch would be helpful :).

[kidd]

For now, I guess the aim is feature parity with as most rust instead of C as we possibly can.

I wouldn't say there's a strong reason why you should use Remacs unless you are already helping the project and want to use it to discover bugs. Myself I'm using remacs exclusively and I haven't noticed any missbehaviour, so it's quite 'safe' to try it.

[marcbowes]

Yup, I get that it's early days still. Surely though, at some point, there should be some tangible benefit to the emacers? I guess what I'm suggesting is just a "why should you use this?" section that is maybe "no real reason yet" and, over time, grows.

Part of the reason I opened the issue was to see if there was a section like that that I just couldn't find.. :)

[brotzeit]

Ooops. I forgot that I can close issues now and didn't look where I was clicking :D

I agree with kidd, you won't have any immediate benefits from using remacs. But I think we will get problems when the current generation of emacs devs retire and there's a better chance that emacs will survive if we try to make it more appealing to young developers. Rust seems to be a good option.

[Wilfred]

@marcbowes great question!

You've summarised the situation pretty well already I think. For contribution, I hope the advantages are pretty clear: friendly community, clear contribution workflow, straightforward Rust APIs.

For users, I hope Remacs will be faster (it's easier to optimise), more robust (we have stronger type checks and the ability to add unit tests), better documented (see #262) and somewhat more featureful (we have some ideas for solving the dumper problem that would allow users to dump their instance as an image) than GNU Emacs.

These benefits aren't available yet. If you use Remacs today, you get to use the latest Emacs features (we track GNU Emacs trunk) and the ability to contribute. I hope you'll be a user, but I understand if you don't feel Remacs is ready for your needs :)

[terlar]

I had a "pleasant" experience with remacs that made me switch over. I had some issue in my configuration that was causing a recursive infinite loop, in emacs it just got stuck and I had no idea what was going on. When I ran in remacs it stopped the execution and notified me that there was a recursive loop. I am not sure if it had something to do with remacs tracking the GNU Emacs trunk (so it comes from a later emacs version) or something implemented in remacs. Anyways, since then I have been running remacs happily.

[marcbowes]

Thanks for that, @terlar!

These benefits aren't available yet.

Yup, this is the core of the question. I totally buy into the vision. The question, really, is which of the end-user benefits are currently delivered. e.g. if you switch to Remacs today you will have X% performance improvement, Y fewer bugs and JSON parsing is 100x faster because it's now native code. Something like that.