openQA VS min-sized-rust

I sometimes look at https://openqa.opensuse.org/ when I'm excited for a new package release (example, kernel 6.5) just to see how far along the next snapshot is. While this is interesting, I can't seem to figure out which packages will be in the snapshot when I do this.

anyway, one great thing about SUSE is openqa.opensuse.org/ which does automatic testing that updates work before releasing....and every pkgs is build using Open Build Service (OBS) which is great as that makes sure Distro has more consistent/automatic binary built

I use Tumbleweed since years and although rolling, its more stable than Pop ever was for me. Stable in the sense of daily use and upgrading in particular. Every update you get on OpenSuse is, as a TLDR version of an explanation, run through an automated AI process that checks if everything works, only then the update is pushed out. The AI analyzes pictures of the OS to check. For example, it goes through the boot process and sees if it works, then clicks on certain apps like yast and see if they open, comparing whats shown on screen with a reference picture. You can see whats currently going on in terms of testing here.

I value Greg KH's Tumbleweed. It does everything I want. Thanks to build.opensuse.org and openqa.opensuse.org . If I had to start from scratch, MicroOs, I would learn along the way.

Rolling release players? openSUSE Tumbleweed (backed/tested by OpenQA before released), EndeavourOS (Arch with an installer; however, this could be too advanced when it breaks)

I would recommend openSUSE (KDE) tumbleweed you get the newest pkgs and they are well tested and they have great tools like openQA, obs, YaST etc. and if you have issue with any updates you can easily just rollback to latest working snapshot

And even though Arch stability heavily depends on the user and package maintainers doing everything right (I'm looking at you TimeShift), openSUSE, being backed by a company, have way more resources and robust infrastructure for ensuring their system is stable than Arch does (I have said this a couple of times, SUSE's openQA is incredible).

Tumbleweed is very current - well, as current as your last update.g/ This means that it's very rare that something is rolled out to the community that hasn't been tested as working.

This is a good guide on building small Rust binaries: https://github.com/johnthagen/min-sized-rust

This talks about going to extreme lengths on making the smallest Rust binary possible, 400 bytes when it was written, https://darkcoding.net/software/a-very-small-rust-binary-ind...

The thing is, you lose a lot of nice features when you do this, like panic unwinding, debug symbols, stdlib… for kernel and some embedded development it’s definitely important, but for most use cases, does it matter?

Oh it was 137, haha. I will link you to this older comment of mine: https://news.ycombinator.com/item?id=29408906

See also https://github.com/johnthagen/min-sized-rust

Are you sure? If so then this is awesome news, but I'm a bit confused; the commit in that min-sized-rust repo adding `build-std` to the README was merged in August 2021: https://github.com/johnthagen/min-sized-rust/pull/30

Are you saying that at that point the feature still hadn't "landed in Rust nightly" until recently? If so then what's the difference between a feature just being available in Rust nightly, vs having "landed"?

Rust binaries are by default nowhere close to 500MB. If they are not small enough for you, you can try https://github.com/johnthagen/min-sized-rust. By avoiding the formatting machinery and using `panic_immediate_abort` you can get about the size of C binaries.

A useful reference: https://github.com/johnthagen/min-sized-rust

That must be without stripping. Also there are ways to reduce binary size. See e.g. [min-sized-rust](https://github.com/johnthagen/min-sized-rust). I've gotten stripped binaries of small cli utils less than 400KiB without doing anything special, less than 150 KiB by customizing profile settings and compressing with upx, and less than 30 KiB by replacing the std with the libc as the link shows. Haven't tried with fltk though...

This is not quite what you're asking, but it does also address the underlying concern: https://github.com/johnthagen/min-sized-rust