boon VS min-sized-rust

I've never yet used kakoune itself, but I've just started using the Meow modal editing package for Emacs, which I'm told resembles kakoune to some similar extent as boon resembles vi.

Shouldn't make much difference, because most of Emacs's default keybinds are either mnemonic or arbitrary (not relative, like Vi's hjkl). There are some unique control interfaces for Emacs which support (and even recommend) alt layouts out of the box. Specifically Meow, Fingers and Boon.

There's also Boon which I like quite a lot but I opted against using mostly because of all the places I would need to type where I wouldn't have access to Boon unless I ported it (a plan I assure you but one lumped behind 1,000 other projects TODO).

https://github.com/jyp/boon

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.

Vim never, ever appealed to me. The keys are not exactly ergonomic, like the WordStar diamond, or intuitive, like the Emacs keys. But I can understand how modal editing - like in WordStar - can improve the writing experience tremendously. So, for my custom Emacs configuration for creative writing, I am using Boon, which allows me to use the left hand home row to navigate characters/words/sentences/lines, and the right hand home row to delete/insert/etc. Pressing v switches to Insert Mode, and C-; switches back to Command Mode. Highly addictively efficient!

I've used both vim and evil in the past, but lately I've been playing with boon and I'm quite enjoying it. It plays nicely with emacs and has some good ideas, like pressing the yank key twice in a row will fix spaces:

I am using Boon, and it has transformed my Emacs experience!

I use https://github.com/jyp/boon which has changed my life.

I am not using Evil in 2022 because I am using Boon :)

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