Comment by adastra22
1 day ago
> It obsoletes the need for a traditional RTOS with kernel context switching
Uh, what does async have to do with hard real-time guarantees?
1 day ago
> It obsoletes the need for a traditional RTOS with kernel context switching
Uh, what does async have to do with hard real-time guarantees?
(Embassy dev here)
You can get preemptive scheduling of async tasks with InterruptExecutor. You create one executor for each priority level, then spawn the tasks in the right one. The latency of the executor and the compiler-generated async state machines is predictable, so you can use Embassy for hard real-time work. See example: https://github.com/embassy-rs/embassy/blob/main/examples/nrf...
Additionally the executor has support for scheduling tasks by priority or deadline within a single priority level. (in latest git, will be in next crates.io release)
It doesn't have anything to do with it. It's some nice syntax over cooperative multitasking.
The README should be corrected then. It is currently making a very false claim.
The claim is you can get embedded concurrency without an OS. Do you disagree?
I prefer C for embedded but must admit that's pretty compelling.
5 replies →
99% people in this thread have no idea what you mean. And that’s the reason projects like these make it to frontpage every other day and have hundreds of upvotes/comments.
And you are downvoted for understanding the issue, of course.
Yup! Which is also the reason why I distrust projects like these in general: bold claims when there is nothing to be backed up with. What else is hiding behind such bold claims?
2 replies →