turbo-resin VS Theseus

Async Rust does definitely work for non-toy use cases. As a data point, we use Embassy for all production firmware at my startup (https://akiles.app/en), using async tasks for everything: Bluetooth, TCP/IP networking, motor control, user interface (LEDs, keypad), a key-value database in flash, stats collection... Async helps with battery life too since it allows putting the core to sleep when no task has work to do, it allows us to build devices with 1-2 years of battery life.

There's other companies using Embassy in production. Sadly firmwares are usually not open source. There's a few non-toy open-source projects using Embassy though:

- https://github.com/nviennot/turbo-resin

I know this exists, https://github.com/nviennot/turbo-resin maybe they already have something documented?

There has been some steady (but slow) progress on an open source firmware for a few popular printers, with one of the goals being to allow multiple file formats. I believe they're still targeting the Mono 4k and Saturn for their first release, but I haven't checked in on the project for awhile.

Yes!! Here's my Rust 3d printer software: https://github.com/nviennot/turbo-resin

There's a nice Photon Mono 4k reverse engineering project by Nicolas Viennot on GitHub where he fixes the crappy touch sensing in the firmware. The goal is to replace the firmware on a variety of chitu-based resin printers with much better open source firmware.

Backstory: I'm writing TurboResin, an open-source firmware for resin 3d printers. We want to support many printers, and one of the difficulty is to understand the electronic board layout and protocols of each printer.

It's coming https://github.com/nviennot/turbo-resin

This is the last part of the reverse engineering series. At this point we are confident that we can finish the firmware to do a print. The firmware repository is here: https://github.com/nviennot/turbo-resin/

There is a project to produce an open source firmware for resin printers TurboResin - it's at a very early stage (not able to actually print yet, but making progress) In time, it should be able to do something similar to what the RERF does and use different exposure times within the same print to strengthen interior parts while leaving surfaces less exposed for maximum detail, which would be very cool!

That's it in a nutshell. I think the pump idea would work but resin is messy so changing resins would be a pain and you would have to clean the lines. Although if you had control of the printer which this project looks well on it's way to accomplishing: https://github.com/nviennot/turbo-resin then you could use the build plate to mix the resin which would simplify things a lot.

Theseus OS (https://www.theseus-os.com/) is also an OS written in Rust. It's a safe-language OS and I believe it's the future of the OSes due to its unique features.

I believe that Tock (tockos.org) and Theseus (https://github.com/theseus-os/Theseus) are in this area a bit as well, just from an actual OS perspective.

I don't know much about this area, but it would be wonderful if these could work with the Libre compute boards, like the AM Logic S905X (Lepotato) or the Rock chip, since they're so much cheaper than a Pi.

We could use some help here: https://github.com/theseus-os/Theseus

Relevant, also an OS written in and made possible by Rust: https://www.theseus-os.com/

I think Theseus is to conventional OSes what Rust is to JavaScript.

I wonder if somehow someday Microsoft Windows can be rerooted as something like wine running in user space of a rust os like https://github.com/theseus-os/Theseus

We've been working on porting Theseus OS to aarch64 over the past few months, feel free to browse our code if you need help understanding anything. Theseus is written from scratch entirely in Rust, so it's likely quite relevant to your work. You can probably find all of the aarch64-related commits and issues just by searching "aarch64" on the repo.

I mean, there are several rust kernel/os projects in progress.

One project that's pushing on the boundary of safety and composability is Thesus, which takes language safety to new ground by shifting traditionally OS-level responsibilities like resource management all the way down to typechecks in the language, and also explores a way of updating any core OS component on a live running system. https://github.com/theseus-os/Theseus

There's also KataOS which google just recently announced: https://opensource.googleblog.com/2022/10/announcing-kataos-...

As you note, these things take time, I agree with sibling that none of them are likely to be "enterprise-grade" or "production ready" this decade.

Not to rain on your parade, but you've essentially just described Theseus OS.