Emacs Eask

Nothing new, but the replacement/alternative to Emacs Cask. :) * Repo link: https://github.com/emacs-eask/eask * Documentation site: https://emacs-eask.github.io/

A comparison to other, similar tools would be useful

[deleted]

In particular Cask, since it is named. Why a replacement/alternative?

https://emacs-eask.github.io/#-why-eask

It seems that every proficient elisp developer will create his/her own framework, because it is the way to achieve *consistency*.

Here you go! :) https://emacs-eask.github.io/#-comparisons

I use [yodel](https://www.github.com/progfolio/yodel) for this sort of thing.

From my point of view, it is all about Windows. I have tried Cask and Eldev since they both declared supporting Windows but I am not getting good experience and it's mostly caused by their behind technology choices. Like Cask uses Python, but Python is particularly bad on Windows, and this isn't Cask's fault. And now their newest version doesn't support Native Windows anymore (you will have to use WSL). Eldev is great and out of the box; the only thing that bothers me is that Eldev would have a short delay on every command since it must start up Emacs to run the task. And I think Cask's DSL design is better than Eldev's config file. I prefer this ```elisp (source melpa) ``` over this, ```elisp (eldev-use-package-archive 'melpa) ``` Eask is very close to Cask + Eldev. **Eask**-file uses the same DSL that Cask has, and it's an Elisp file like Eldev config. Behind technology choices are NodeJS and JavaScript, which can compile into native executables. Unlike Eldev, it will first be parsed by the JavaScript layer (Eask uses yargs) so it wouldn't go through and start up `emacs.exe` directly. Some commands would even avoid doing it (mostly cuz it's unnecessary).

That sounds great. Thank you for your explanation.