ryo-modal VS min-sized-rust

To build on what others are saying about Emacs, if you start exploring the package ecosystem, you're going to see quite a lot of really interesting packages that are related to improving/experimenting with the UX of editing text. While I'm not endorsing anyone in particular, I think what this list does show is just how easy it is to do pretty much whatever you want in Emacs;

https://karthinks.com/software/avy-can-do-anything/

https://github.com/jyp/boon

https://github.com/clemera/objed

https://github.com/jmorag/kakoune.el

https://github.com/meow-edit/meow/

https://github.com/xahlee/xah-fly-keys

https://github.com/Kungsgeten/ryo-modal

https://github.com/emacsorphanage/god-mode

Emacs 29 also now has treesitter and LSP mode integration built-in, a compilation mode, a comint mode for REPLs, excellent file browsing packages (I use dired/dirvish), and a few other killer features.

Now, if what you truly dislike are "quirky editors", prepare yourself for a world of hurt because vanilla Emacs departs quite a bit from "modern" text editors. I struggled with this for a while, but eventually by buying into the paradigm, I now feel that when emacs try emulating "modern" IDE features like autocompletion, LSP, and DAP UI, I feel like it's a regression, not a progression. The point here is that you might have an "idea" of what good initial UX and lack of quirks would look like, but Emacs might change the way you think.

If it's the latter and you're looking for a way to set up vim/evil like keybindings yourself (separate links for each), Modalka, RYO-modal, and Meow (and probably a few dozen others 'cause emacs) allow you to do that.

You can write custom commands that wrap a little bit of logic around the standard movement commands. Or another option would be to look at ryo-modal or meow.

Along with General, you can take a look at some other packages for keybindings and modal editing. A good option is RollYourOwn Modal mode. In the documentation there, it also lists several other packages with pre-defined bindings. Xah-Fly-Keys is specifically designed for ergonomics and may be interesting to explore.

Because you can roll your own modal mode. This particular approach will make the experience convenient in the way you actually prefer (Emacs' extensibility at its finest) and it'll allow you to slowly move towards the modal editing if it happens to be convenient for you.

Similar to Meow is ryo-modal. What I like about ryo-modal is that it is completely unopinionated and does nothing by default, and instead just provides the tools to make your own modal editing system.

I was thinking that combining this functionality with something like ryo-modal could make for a very satisfying and efficient modal keybind system. However, it doesn't seem like there's any ready made way to do this in Emacs.

ryo-modal is a package for creating modal keymaps. I want to test it, but I need a little help.

This is a good guide on building small Rust binaries: https://github.com/johnthagen/min-sized-rust

This talks about going to extreme lengths on making the smallest Rust binary possible, 400 bytes when it was written, https://darkcoding.net/software/a-very-small-rust-binary-ind...

The thing is, you lose a lot of nice features when you do this, like panic unwinding, debug symbols, stdlib… for kernel and some embedded development it’s definitely important, but for most use cases, does it matter?

Oh it was 137, haha. I will link you to this older comment of mine: https://news.ycombinator.com/item?id=29408906

See also https://github.com/johnthagen/min-sized-rust

Are you sure? If so then this is awesome news, but I'm a bit confused; the commit in that min-sized-rust repo adding `build-std` to the README was merged in August 2021: https://github.com/johnthagen/min-sized-rust/pull/30

Are you saying that at that point the feature still hadn't "landed in Rust nightly" until recently? If so then what's the difference between a feature just being available in Rust nightly, vs having "landed"?

Rust binaries are by default nowhere close to 500MB. If they are not small enough for you, you can try https://github.com/johnthagen/min-sized-rust. By avoiding the formatting machinery and using `panic_immediate_abort` you can get about the size of C binaries.

A useful reference: https://github.com/johnthagen/min-sized-rust

That must be without stripping. Also there are ways to reduce binary size. See e.g. [min-sized-rust](https://github.com/johnthagen/min-sized-rust). I've gotten stripped binaries of small cli utils less than 400KiB without doing anything special, less than 150 KiB by customizing profile settings and compressing with upx, and less than 30 KiB by replacing the std with the libc as the link shows. Haven't tried with fltk though...

This is not quite what you're asking, but it does also address the underlying concern: https://github.com/johnthagen/min-sized-rust