aniseed VS moonscript

aniseed

You don't need to transpile it if you use https://github.com/Olical/aniseed

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.

Just use vim. Yes, emacs has a lisp engine, but so does nvim[1]. Really, though, using vim properly means that it doesn't need to swallow the kitchen sink[2]. Just use vim.

1: https://github.com/Olical/aniseed

2: https://blog.djha.skin/p/emacs-users-im-okay-i-promise/

I use Aniseed to write my configs in Fennel, and I can't seem to find a way to get Aniseed bootstrapped and managed by lazy. Folke has said that fennel isn't supported in issues about hotpot and tangerine, but neither of them particularly help me solve my issue

:!git clone https://github.com/Olical/aniseed /home/USER/.local/share/nvim/site/pack/packer/start/aniseed Cloning into '/home/USER/.local/share/nvim/site/pack/packer/start/aniseed'...

Have you tried aniseed ?

Aniseed: mostly an environment, it does handle configuration. It adds a lot of clojure features (another modern Lisp) such as a module system. It does seem to be slower to startup though, but I really like how its module system works and still use it for that reason alone. There's not much boilerplate code, just add it to the header

The easiest would be to use aniseed: https://github.com/Olical/aniseed, it has a bootstrap script that downloads all the needed dependencies: https://github.com/Olical/aniseed, it also adds some syntax niceties and testing support. Here's an example of a plugin: https://github.com/katawful/kat.nvim

Now I like lua, and think single pass is the way to go for interpreted, since you don't have the disadvantage of a slow compile time no matter how big your codebase gets, BUT its not great to write in. things like +=, ++, are not possible, which means the only solution is to transpile into it, which has led to some good languages like moonscript[0], teal[1] which offers static type checking, an absolute must as your codebase grows.

[0]: https://moonscript.org/

That can be very productive and clever, but be - and stay - aware that such polyglot solutions tend to be maintenance headaches in the longer run.

There is a really nice open source project out there that allows you to train your hearing and your sightreading, but it's written in the authors own language which in turn compiles to JavaScript and the headache to set up their toolchain is such that I haven't bothered fixing any of the bugs that I'm aware of (and there are plenty).

https://sightreading.training/

https://github.com/leafo/sightreading.training

It's written in a language called 'Moonscript':

https://github.com/leafo/moonscript

Which compiles to Lua. Which compiles to JS.

Madness. Nice madness, but still, it stopped me from being a contributor.

RE: the cost of switching at this point, what about languages that compile to Lua? Like https://moonscript.org/. That would let you keep the legacy code, no?

In the case of Lapis, it is actually written in Moonscript, which needs a few more things.

There's also some languages made to compile straight to Lua: - MoonScript is the most popular Lua wrapper - it's built to be more Python-like, featuring indentation-based scopes, function calls without parentheses, lambda syntax, list comprehension, and much more. - Yuescript is a modern update to MoonScript that adds more features (I haven't used it myself, so I'm not entirely sure exactly how it differs from MS). - Teal is a version of Lua that adds static typing for better code standards.

A programmer-friendly language that compiles to Lua.

This is a sample code for learning, written in Moonscript for TIC-80: