cib VS bottlerocket

[2]: https://tbfleming.github.io/cib/

Here are some more ports of LLVM and clang to the browser:

* https://github.com/kripken/llvm-js

* https://github.com/tbfleming/cib

* https://github.com/jprendes/emception

LLVM just does pure computation, really, so it's not hard to port to wasm - much simple than say Python (which has also been ported several times). The only challenges with LLVM are the build system (which has self-execution), working around some issues like clang wanting to open a subprocess, and adding some ifdefs.

That is half of what I would need for a project, the other half being Clang itself running in the browser (to use for teaching), in theory there is [1] since many years, but in practice it never worked for me (even now I get "Runtime error: memory access out of bounds")

[1] https://tbfleming.github.io/cib/

It seems that there's a project doing exactly that: https://github.com/tbfleming/cib

It takes some work (mostly due to LLVM building code to run later in its build system as it goes), but it's very feasible. LLVM has been ported to Wasm (and before that to JS) many times, for example:

https://github.com/jprendes/emception (2021)

https://github.com/tbfleming/cib (2017)

https://github.com/kripken/llvm.js (2012)

I agree it would be great to see this repl running 100% in the browser!

According to this discussion - starting with Bottlerocket 1.13.0 (Mar 2023) new distributions will default to using Cgroups v2 interface for process organization and enforcing resource limits.

Well, the link I provided references the Bottlerocket docs which explains the control container and the admin container and also how you can configure Bottlerocket via the User Data field when launching it as an AMI. All the information appears to be in the docs

https://github.com/bottlerocket-os/bottlerocket/blob/develop...

On the server-side, there's Bottlerocket OS [1] (Amazon). They use A/B partitions for upgrades, and the idea is that you just run containers for anything non-base. Boot containers are used to do custom configuration at boot, and host-container (or DaemonSet, if you run K8S) is used for long-running services.

[1] https://github.com/bottlerocket-os/bottlerocket

Bottlerocket OS.

To add to the other excellent answers, I would recommend adding Bottlerocket to your reading list: https://github.com/bottlerocket-os/bottlerocket#readme

I'm also aware of (but haven't used) https://github.com/siderolabs/talos#readme

I just realized your question may have implied a desktop os, whereas Bottlerocket, Flatcar, and likely the others in this specific thread are server-side. I don't have much experience with trying to solve that problem on the desktop except for the horror-show that is snap

https://github.com/bottlerocket-os/bottlerocket/issues/2855 soon for bottlerocket, maybe you’ll see Amazon Linux 2023 for eks nodes soon too?

I think open sourcing for free labor is a common misconception. Most corporate led open source projects (eg, https://github.com/bottlerocket-os/bottlerocket from AWS or https://github.com/facebook/relay from Facebook) still require a team of employees.

Bottlerocket might be worth a look. https://github.com/bottlerocket-os/bottlerocket