Rhai VS RustPython

The OS would be built in Rust and the module system could be made using ELF executibles (fast, but it could be really hard to implement modules to communicate with the kernel), WASM (can compile from many languages, slower but not too slow, APIs can be simple enough to implement if the correct VM is choses) or even a custom scripting language like rhai (slower, but best way for the implementation [way to connect modules and kernel]).

For sure, that's where something like rhai would shine: https://crates.io/crates/rhai

Oh yeah, for sure. But there are rust based scripting languages that are designed to interop with rust, such as rhai: https://crates.io/crates/rhai

Markdown support Markdown as a templating language is supported, and you can use global and local configs. Also, there are several built-in helpers, and you can make your own, in the language rhai

I came across this library lately which might be close to what you’re looking for: https://github.com/rhaiscript/rhai

We have already re-written the Python Interpreter in rust. Javascript will be just too easy to re-write in rust, fear not for we have already re-made nodejs in rust; aka Deno.

Quick note - CPython is the OG and most popular implementation of Python, but it is not the only implementation of Python. Some other fairly well-known examples are Jython (Java implementation), RustPython (Rust implementation), or the more mind-bending PyPy (Python implemented via Python 🤯). Python is an interpreted language, and you can think of all these different Python implementations as being different implementations of the interpreter itself. The interpreter is the program that takes your Python code and executes it via a virtual machine. This differs from a compiled language (like C) which needs the high-level C code to first be converted to machine code and then executed by the CPU.

lalrpop is great. It's a completely different approach from nom, but for parsing a programming language, I would at least consider it. RustPython uses it.

I still understand the priorities, there was lately some significant effort to improve performance ( and this gave this kind of hilarious extrapolation Python 3.14 Will be Faster than C++ - totally a clickbait, sorry ) - and they're still improving everything that makes static analysis reliable. So while I say I wish I have to respect the decisions that the core team are making, it paid off so far. There is also a very active community rewriting the interpreter in rust, this blows my mind. We have also to consider what happened to Perl. Perl 6 was a big retro-incompatible rewrite and ... it's basically dead now.

I mean, it already has happened. Now obviously that doesn't mean cpython is going to get replaced by a rust version any time soon, but I'd be cautious about saying never.

Well, there's rustpython

RustPython already exists for those who want it, it's totally possible there's a future world where it's more popular than CPython and people switch, but it's pretty unlikely https://github.com/RustPython/RustPython

Honestly, my fantasy IDE would be something very much like emacs, but ported from the ground up in rust and streamlined a bit to avoid some of the bloat, and using RustPython for scripting the layers, including a badass kakoune/helix emulator.

I’m still hoping out hope for something like RustPython https://rustpython.github.io. Using Python to extend SublimeText over the years has been amazing. I have tons of little helpers that were dirt simple to write. I would love to see Helix adopt a known and popular language that’s easy for anyone to use rather than something obscure like Rhai.