Can confirm. It hasn't turned me off Emacs by any means, but it is one of the reasons I strongly prefer releasing packages on MELPA to getting patches into Emacs proper.

Neovim came along but majority who use vim still use vim. They won't change. This is in a situation where neovim is ahead of vim in certain areas (some may not like it and call it bloat but I call them features).

Unless remacs gives a clear advantage over emacs in terms of performance while still retaining compatibility people won't switch easily. Even then the switch should be quick and painless. (Neovim had those and so some people jumped ship).

I would never use Remacs but I would use CLemacs. Others wouldn't use the previous two but would use Pymacs, Rbemacs or Hemacs. Then there's people who wouldn't use any of those but swear by Elmacs.

You're aware that remacs rewrite the C part of emacs in Rust, not the ELisp ones? The final goal for users and plugin writers is a fully transparent transition.

That's true but it's only the technical and logistical part of the problem.

There's a moral issue too in giving-up copyright to an entity : What if the future the FSF (RMS is not eternal) changes its policy to turn to something completely crazy with your code ? They will own all will own all your copyright-assigned code and you won't be able to do anything about it.

I mean : what if you were agree with GPL2 but not 3 and that now the copyright owner decides to move the code you've written to GPL3 ?

>What if the future the FSF (RMS is not eternal) changes its policy to turn to something completely crazy with your code ?

The FSF's copyright assignment contract has clauses that prevent them from doing such things. It's really a very fair contract.

To elaborate: the clause is actually designed precisely to prevent a hostile takeover from another entity; it's an important part of the contract. The clause states the conditions under which your code and program will be made available.

Ok this seems more reasonnable than I thought.