tamago VS s2protocol

There's two major production-ready Go-based operating system(-ish) projects:

- Google's gVisor[1] (a re-implementation of a significant subset of the Linux syscall ABI for isolation, also mentioned in the article)

- USBArmory's Tamago[2] (a single-threaded bare-metal Go runtime for SOCs)

Both of these are security-focused with a clear trade off: sacrifice some performance for memory safe and excellent readability (and auditability). I feel like that's the sweet spot for low-level Go - projects that need memory safety but would rather trade some performance for simplicity.

[1]: https://github.com/google/gvisor

[2]: https://github.com/usbarmory/tamago

Of course it can, there are companies shipping products written in bare metal Go.

https://www.withsecure.com/en/solutions/innovative-security-...

https://github.com/usbarmory/tamago

For comparison, what are the differences in goals and approach with Tamago? https://github.com/usbarmory/tamago

I've been keeping an eye on TinyGo (Go compiler that targets microcontrollers and uses LLVM) and also TamaGo (allows you to run Go on bare metal, without any C dependency).

If you want to go deeper, there is also bare-metal Go runtime for rpi (among others): https://github.com/f-secure-foundry/tamago

> just proves your lack of knowledge

Tone is not needed.

For TamaGo, it seems to allow developers run their application, not build an OS on the hardware. But I have not played with it, you are right.

> TamaGo is a framework that enables compilation and execution of unencumbered Go applications on bare metal

The environment does not seem to allow building a generic operating system [1]. F-Secure ported the runtime itself to boot natively. But please correct me.

> There is no thread support

The environment you run in is specifically curated for Go applications, such as the memory layout. I'd call this an "appliance" rather than enabling Go to be used for full-fledged generic operating system implementations.

[1] https://github.com/f-secure-foundry/tamago/wiki/Internals

I used mpyq and s2protocol as reference implementations and ported them to Rust.

vm = virtual machine/memory?

I'm porting this Python library to Rust: https://github.com/Blizzard/s2protocol.

For the shitty, first pass prototype code I've written so far I've seen a ~30-40x speedup compared to the Python implementation and a ~2x speedup compared to a Go implementation by someone else: https://github.com/icza/s2prot.

That is why I chose Rust over a GC language like Go. It's a lot faster out of the box, even without me having a strong understanding of memory operations.

You got programming knowledge? I'm not trying to dunk on you but if you don't know how these work then you won't be able to build the thing anyway. First result when you search for stuff is the official Blizzard s2protocol parser https://github.com/Blizzard/s2protocol

same, the main thing we need is the equivalent of https://github.com/Blizzard/s2protocol for stormgate.

React basics are not that complicated. I ported the core functionality of this Python library to Rust in ~1w with zero prior Rust experience, and I definitely think Rust is more complicated than React.

pip install s2protocol (this is a blizzard vended package for parsing replay files - see https://github.com/Blizzard/s2protocol)

If not you will have to either learn programming, this tool by blizzard is capable of extracting replay stats: https://github.com/Blizzard/s2protocol