inline-python VS embassy

If you're willing to go the meta programming route, Rust is pretty flexible too. You can literally run python inline using macros.[1]

In my experience as someone that has been using Rust for a few years (and enjoys writing Rust) the biggest issue regarding adoption is that async Rust just isn't there yet when it comes to user experience.[2]

It works fine if you don't deviate from the simple stuff, but once you need to start writing your own Futures or custom locks it gets to a point that you REALLY need to understand Rust and its challenging type system.

[1] - https://github.com/m-ou-se/inline-python

This may be cursed but you could just use https://github.com/fusion-engineering/inline-python to use the Python Levensthein library in Rust directly. Just make sure to invoke the Rust binary under a venv with the library

I know the OP asked about Node/PHP but for Python, there is https://github.com/fusion-engineering/inline-python which can give you both Rust and the all-the-libraries experience.

Inspired by past work: LINQ, inline-python, crepe, DataScript, Riffle.

And if that doesn't work, there's always inline-python.

well, Rust didn't do the same thing for a reason. Rust lets you pick and choose what async runtime to use (even though everyone has decided to use Tokio anyways). This is good because it allows for alternative async runtimes like Embassy (https://embassy.dev/) and it also doesn't freeze the API into something that can't change. It could totally be possible that people find a new style of async that works better than std::execution.

Embassy got _some_ support for rp2350 for quite some time now

https://github.com/embassy-rs/embassy

TL;DR: No. Maybe? Depends.

It's probably reasonable to make a distinction between "Real Time" desktop/server OS (on CPUs) vs "Real Time" embedded hardware OS (on MCUs).

(Even aside from any hard-/soft- real time distinction.)

On the embedded side, in addition to FreeRTOS (upon which Pebble OS is built), I'm aware of others with reasonably high profile such as:

* Zephyr (Linux Foundation, C): https://en.wikipedia.org/wiki/Zephyr_(operating_system)

* NuttX (Apache Software Foundation, C & C++): https://en.wikipedia.org/wiki/NuttX

In addition, there's also some "up & coming" Rust language projects which fall somewhere along the "framework" to "OS" spectrum (in part, via https://arewertosyet.com):

* Tock: https://github.com/tock/tock

* Embassy: https://github.com/embassy-rs/embassy

* Hubris: https://hubris.oxide.computer

On the desktop side, I seem to recall in the past, OS such as BeOS & QNX have been presented as a possible future for real time desktop OS that hasn't arrived.

As someone else already mentioned, PREEMPT_RT being merged for Linux is a recent development somewhat in this space which could have impact on both desktop & "embedded" situations but suitability varies dependent on, say, whether you're wanting to use it for audio production versus controlling some 10 tonne robot operating next to humans.

Hope this at least goes some way to answering your question. :)

The other comment implied it but I think it's worth pointing out that:

> embedded applications that can't have asynchronous execution

Is most definitely not the case.

They can't have the same type of async runtime that would be optimal for a web server or the likes (and I'm not sure all desktop applications and web servers are going to always benefit from the same runtime in the same way), but that's a point in favour of Rust's model imho

If you're interested this is an embedded async runtime that's expected to run in no-std and no-alloc environments

https://embassy.dev/

In this article, I will guide you through creating a Snake game in embedded Rust on the BBC Micro:bit using the asynchronous framework Embassy.

Rust solved this by autogenning code from mfgr published device xml descriptors. Eg https://embassy.dev/

Better than any C(++) embedded hal I've used