lumen VS doom-emacs

The BEAM (runtime?) is written in C. There is also an effort to rewrite it in Rust (https://github.com/lumen/lumen). Some functions are built into the VM but most of the supporting 'standard library' (OTP / Open Telecom Platform) is written in Erlang. The (main) compiler is written in C. So it's all C or Erlang afaik.

It is ported to every major flavour of OS.

I don't know what 'back end' means in this context.

There are attempts to implement an Erlang/BEAM-inspired reactor/runtime/executor/ecosystem for Rust's Async, in particular Bastion. (There are also Lumen, Lunatic and Async-Backplane/Async-Supervisor.)

If I recall correctly, Saša Jurić mentioned in an interview that he envisions the BEAM being used as an OS in the future, where you can run your database, web server and other services under one VM.

While I don't personally have much use for it (at the moment), I'm curious about how this would look like with Lumen [0] where you can run your whole web stack with a single binary and being internally supervised by the BEAM.

Lumen's development has been slow but I remember seeing a tweet from a team member stating that development is slowly ramping back up (not a criticism in any way, just providing some context).

[0] https://github.com/lumen/lumen

If you can't find a way forward, you could always peek here: https://github.com/lumen/lumen

Lumen: Alternative BEAM implementation, designed for WebAssembly\ (11 comments)

The performance lag of Spacemacs was addressed by Doom Emacs ( https://github.com/hlissner/doom-emacs ). Have you tried Doom Emacs by any chance. After syncing everything, the performance is stellar in my opinion.

but I just realized, you're probably better off using doom emacs. The defaults are sane, customizations are almost always optional and the community's really active/helpful. (Disclaimer: I'm a doom emacs user with ~2k lines of config)

While Doom is more opinionated, it's not too difficult make Emacs your own, most of the choices are optimized anyway. Currently the head of Spacemacs devs is not active on the project anymore. Also I don't think it's hard to upstream code to Doom, as long as the code is thoroughly written, take a similar example on both sides: the introduction of a completion engine as layer/module (same packages are installed): - https://github.com/syl20bnr/spacemacs/pull/14901: 23 comments, 7 participants - https://github.com/hlissner/doom-emacs/pull/4664: 576 comments, 20 participants

You should definitely mention Doom Emacs - it will make Vimmers instantly feel at home.

Also Doom emacs has one. https://github.com/hlissner/doom-emacs https://github.com/hlissner/doom-emacs/tree/master/modules/lang/common-lisp

Nowadays, I use https://github.com/hlissner/doom-emacs with WSL2 but only for org-mode. For code, I have either Sublime Text or VS Code.

In doom emacs I use workspaces https://github.com/hlissner/doom-emacs/blob/develop/modules/ui/workspaces/autoload/workspaces.el

This was reported and fixed yesterday: https://github.com/hlissner/doom-emacs/issues/6320. Update Doom.

I've been using Emacs(Doom Emacs) for Golang development for a while and everything is good so far, but I really have troubles when I use it to explore Kubernetes source code today, everything is very very slow which makes the entire editor almost unusable: gopls seems not respond at all, guru eats all of the CPU but all features just not working, and I even got the following error messages for simple saving:

I use bottom instead of htop. I am using most of my time in terminal. I am using the window manager just to visually see my different terminals operate at the same time! I also use doom-emacs (emacs in 'evil mode', that is with vim keybindings. works very well supporting org-mode). I also use terminal version of vim, and i am actively searching for new terminal tools and cli programs with tldr pages.