nyoom.nvim VS Fennel

The oxocarbon theme and color palette originally started off as something fun I'd use for https://github.com/shaunsingh/nyoom.nvim/tree/main, which was still just a set of dotfiles at the time and not the pet project it is today. I never imagined how many people would want to use it. Previously the theme was written in rust, mainly because I wanted to play around with nvim-oxi.

I use fennel as well, through my own WIP neovim framework (https://github.com/shaunsingh/nyoom.nvim). I highly recommend trying out lisps, it's not for everyone but personally for me I find it much easier to prototype code. It's reached the point where I end up using fennel for a good portion of my scripting tasks

Thats awesome! I have a simpler, non-gui version that I use based on hsluv in my dotfiles: https://github.com/shaunsingh/nyoom.nvim/blob/main/fnl/modules/ui/nyoom/colorutils/init.fnl.

Nyoom - It's a fun little name. Not supposed to mean anything images - Its a neovim config? not sure what you want me to do with it Reddit post - I mean I could write a page about it but thats just a repeat of the readme GitHub repo - https://github.com/shaunsingh/nyoom.nvim

For ease of use, you can use conjure for evaluating the code, cmp-conjure for nvim completions, hibiscus.nvim and nyoom.nvim macros for macros, and you can also use nyoom.nvim as a base config.

My personal configuration is also written in fennel if you would like to take. look: https://github.com/shaunsingh/nyoom.nvim. Neovim's come a long way in what you can do with it. Fennel has a macro system as with any lisp, so you can make the syntax feel right at home with emacs https://github.com/shaunsingh/nyoom.nvim/tree/main/fnl/macros. You can even create dynamic-module like integrations with rust programs (see https://github.com/shaunsingh/nyoom.nvim/blob/main/fnl/parinfer/init.fnl, interacting with https://github.com/eraserhd/parinfer-rust/tree/master/src)

The config follows the ideals of Doom Emacs: - Minimalistic good looks inspired by modern editors. - Modular organization structure. (eventually, I want to make sets of packages into modules like doom does, but thats blocked by https://github.com/bakpakin/Fennel/issues/413. You can see some broken work here: https://github.com/shaunsingh/nyoom.nvim/tree/module-rewrite) - Opinionated, but not stubborn. Sensible defaults and curated opinions, but feel free to change them up (or entirely disable them!) - Your system, your rules. You know better. At least, Nyoom hopes so! There are no external dependencies, and there never will be.

It's interesting: minimal software is out there, but folks don't tend to choose it. I spend a fair amount of time thinking about how to be conservative in my dependencies, and this encourages a lightweight stack that tends to perform pretty well. These days, I'm favoring tools like Lua, SQLite, Fennel[0], Althttpd[1], Fossil[2], and the Mako Server[3] and find that great, lightweight, stable, efficient software is to be had, for free, but you have to go a bit off the beaten path. This isn't stuff you hear about on Stack Overflow.

In terms of frontend, which the post focuses on (Google Docs and a 30MB doc), I guess I'm conflicted. While I tend to favor native apps + web pages, I'm also a daily Tiddlywiki user, and I really think web apps have their place (heck, one idea I'm working on is a lightweight local server that lets you run web apps like Tiddlywiki). But without a doubt, Tiddlywiki is more resource intensive than Emacs (my go-to for notetaking when I'm not on TW). My tab for a 6MB Tiddlywiki file uses 155MB of RAM, and my (heavily customized, dozens of open buffers) Emacs session uses 88MB. So I do think the author has a good point.

[0]: https://fennel-lang.org/

Eh it's not just luajit and luajit didn't create that problem either. It's a symptom of lua actually succeeding at its design goal of being easily embedded as an extension language. A significant number of incompatible runtimes are more popular than the most recent puc lua, including I believe the older official lua 5.2 released in 2011.

I've done a fair bit of professional lua development and I don't think I've ever written standalone up-to-date puc lua except maybe for some tooling & scripts. It's such a small language and used in such a way that the runtime, distribution method, and available APIs have much more impact on your use (and compatibility) than the version.

Virtually everyone shipping a lua environment is also shipping changes to it that make it a unique target, if only extensions to the standard library. This is why I think syntax layer-only approach like fennel's is the correct choice for improving on lua. It mirrors lua's runtime semantics exactly, and allows you to access the implementation peculiars on their own terms and so can just be run on time of any lua system.

https://fennel-lang.org

Just learned about https://fennel-lang.org/ , could have probably used that as well to avoid Lua.

> I’m positive that there is a Lispy language out there (actually in existence, or the aether) that is appropriate for embedded work, but the constraints of the target make it difficult to envision.

Perhaps Fennel* fits the bill?

* https://fennel-lang.org/

I've also seen neovim plugins written in fennel [0], so if you want something lispy, that's possible now.

[0]: a Lisp that compiles to Lua, https://github.com/bakpakin/Fennel

Something similar: Fennel (https://fennel-lang.org/) is a lisp that compiles into Lua, which nvim can use as plugins, so you can write nvim plugins in a lisp. Aniseed (https://github.com/Olical/aniseed) makes this really easy.

If you want a more FP language on the Lua runtime, you might be interested in Fennel. I wrote a post about adding Fennel compiler to a hslua interpreter a while back, which might be useful for you.