vodon-pro VS tock

I'm the author of a free open source video player project called "Vodon Pro", it's written using Electron. You can see the functionality of it here: https://vodon.gg/ (source here: https://github.com/Rodeoclash/vodon-pro)

You know I don't make any money off this right? You can download the entire app for free and the source code for it if you want (https://github.com/Rodeoclash/vodon-pro)

I have a video player designed for esports coaches to do gameplay reviews of matches that their team has played. It has the unique feature that you can synchronise multiple viewpoints from a match together. It's free and open source.

https://github.com/Rodeoclash/vodon-pro

I've built it using Electron as an MVP but I'd like to rebuild the most successful features into a native app using gstreamer as a V2 version at some point.

I'm looking for help with reaching more esports teams that might be interested in using it, graphic design feedback (I've done it myself :/ ) and someone who has knowledge building native apps that I could bounce ideas off.

Vodon Pro can be downloaded, for free, from https://github.com/Rodeoclash/vodon-pro

[1] https://github.com/Rodeoclash/vodon-pro

I'm using the build of this app to evaluate rebuilding another app I have called Vodon Pro which is a synchronised video player for esports reviews (https://github.com/Rodeoclash/vodon-pro) into QT so the performance is better but also that I can leverage GStreamer using the QT sink here: https://gstreamer.freedesktop.org/documentation/qmlgl/?gi-language=c

If you're interested, you can download it here: https://github.com/Rodeoclash/vodon-pro

Hi! This is Daniel from OxidOS Automotive (stating this for disclaimer purposes).

Yes, our OS is based on TockOS, and our CEO (Alex Radovici) is #7 in the contributors list (https://github.com/tock/tock/graphs/contributors), with other colleagues contributing in the past years.

I'm definitely not the best person to answer this, but honestly it's not bad. Here's an example of a moderately complex peripheral, the cortex-m MPU, and how one rust OS handles it:

https://github.com/tock/tock/blob/3a0527d586702b8ae8cb242391...

Reads and writes turn into volatile reads, so everything works out under the hood. You get the benefits of everything having good names, declared sizes, and proper typing on your register accesses. You can extend that to bit accesses as well.

Rust still has a few areas it isn't competitive in, like your hyper limited or obscure chips (e.g. 8051s, XAP), mature tooling around formal methods, and a certification story for safety critical code. People are working on these latter two issues (e.g. ferrocene) and supposedly very close to public delivery, but you know how slow the industry is to adopt new things even then.

There's Tock (https://www.tockos.org/), which is written in Rust (with sprinkles of assembly).

Yeah, and I like I mentioned in the earlier comment, omitting the frame pointer reduces code size by 10% on RISC-V targets, which is huge when dealing with embedded flash: https://github.com/tock/tock/pull/1660

Tock is an excellent embedded OS written in Rust and has some good industrial support. I think Tock gets a lot of stuff right and I highly recommend some of the talks the developers gave on it.

Unfortunately, it increases the code size by 10%. I was looking into this just last week, and can confirm that it's still a problem on the latest version of Rust nightly: https://github.com/tock/tock/pull/1660

I wish we could have frame pointers, because they would make working in embedded land so much easier and more reliable, but a 10% increase in code size just isn't worth it.

TockOS was the first rust RTOS I found. Coincidentally, it has had support for the esp32c3 for over a year now.