kernel-wasm VS visual-regexp-steroids.el

WASM is not related to JavaScript in any way, it's just a formal definition (see the spec) for a bytecode and a VM that executes it. One of the problems that WASM tries to solve for web development is to get away from JS because it's such a mess. It's unfortunate that WASM has "Web" in its name, as it's rally not just for Web: there are many embedded runtimes, for example, popular proxy server Envoy supports WASM for writing filters (aka extensions) and there's even WASM runtime for the Linux kernel.

Wasm started in the web, but has since been ported even to the Linux kernel [0]. It seems perfect for situation where you near machine code levels of performance, but don't want to carry different binaries for different CPU architectures - exactly what you want from a plugin system. It also allows far greater isolation than "real" compiled code.

[0] https://github.com/wasmerio/kernel-wasm

That is a cool tool. If I can use visual-regexp-steroids.el to manage regex matching in emacs (I need to figure out how to do this if this is even possible), but also I do not understand what I need to change in the variable org-emphasis-regexp-components. The variable is described as the following....

https://github.com/benma/visual-regexp-steroids.el/. There is always a package for what you need in emacs or you can always make your own. This package supports python regex in emacs which supports look ahead/behind and alot of other things.

Note at the bottom of emacswiki.org/[…]/RegularExpression that with python available, you can use visual-regexp-steroids to get access to sufficiently-expressive regexp.

I use visual-regexp-steroids to allow searching and replacing with alternative syntaxes (specifically, PCRE). It really makes the experience better along with visual-regexp itself.

Probably by using pcre2el. There is also visual-regexp-steroids which lets you use python engine as well (aside from pcre2el) and achieve the same thing shown here but interfacing with python.