@michalfita @anselmschueler @renormalist @aliceif @bill88t @BrodieOnLinux @AsahiLinux @landley

Yeah the extensive dependency on #Cargo and poorly declared or undeclared dependencies ain't a failure of #Rust entirely...

• Rather it's 99% the blame of #developers and 1% the blame of Rust for normalizing this Internet-centric setup, which had been introduced with even worse systems like #pip and #npm but that's beyond the scope of my criticism.

Point is I want to develop @OS1337 into a minimalist #toybox + #musl / #linux distro which excels with #minimalism and #Reproduceability of everything.

• This does make things more convoluted since it basically means that every application needs to be it's own, self-contained & statically linked binary, but alas this is more of an edge-case than the norm.

@bananapi does it alt least come with @RaspberryPi / #RapsberryPi-level #documentation #quality and it's #drivers mainline'd in the #Linux #Kernel?

• Cuz #Reproduceability is a problem and support isn't done with just releasing some random image to dd and then abandon #Hardware & #Firmware...

(Yes, I'm still angry for the #BananaPi0M2 at you!)

@petersuber @openscience +1

I think #reproduceability and #OpenData should be mandatory #transparency in terms of #science, discouraging "#LyingWithNumbers" and encouraging a healthy discussion re: data sources as well...

@landley @SweetAIBelle so yeah, I think #transparency is something #FLOSS can and should deliver more by virtue of enabling #ReproducibleBuilds and -Setups!

We expect #Reproduceability in #mechanics, #electronics and any other #engineering as well, and we should do that with #Software, #Hardware and #Firmware too because it not just removes the need to #trust but also allows for longer support...

So instead of demanding a #remote-#updateable shite that can literally enable maliciois actors to "Hastings" drivers, @EU_Commission should've rather demanded #ReproduceableFirmware and that all the componemts, design and Software to be #OpenSource'd permissively to enshure #LongTermSupport and #compatibility and ease of testing for anyone from Users amd 1st party service centers to 3rd Party repair shops to Historic Vehicle owners...

Not to mention that OS/1337 should really excel with #transparency and #reproduceability in that the first #release should be completely possible to #DIY from scratch by running a single #bash script that yoinks said sourcecodes, .config files and in the end spits out a working & #bootable #1440kB 3,5" #FDD image.

Nothing fancy but something useable - even if it's just a #dropbear #SSH #Client (aka. #dbclient) and the basic #toybox tools to get #IPv4 connectivity.

#OS1337 #Linux #embedded