U tweetove putem weba ili aplikacija drugih proizvođača možete dodati podatke o lokaciji, kao što su grad ili točna lokacija. Povijest lokacija tweetova uvijek možete izbrisati. Saznajte više
Happy holidays, everyone.
I have a wish to make for 2020 and it's about further proliferation of Rust in firmware space.
@vincentzimmer recently blogged about the effort to make Rust into a first-class language for EDK2 (http://vzimmer.blogspot.com/2019/12/rust-oxide-corrosion.html …), and that work makes me happy.
I'd like to thank everybody working on RustPkg (https://github.com/tianocore/edk2-staging/tree/edkii-rust/RustPkg …) and hope that it will get out of staging and adopted by IBVs and OEMs alike, as after 20 years of writing security-critical system software in C, it's finally time to switch to a safer better tools.
I consider EDK2 support as the most important step in a long way of actual industry-wide Rust adoption, but I'd also like to thank other firmware folks for making steps in the same right direction, i.e. @system76 for https://github.com/system76/firmware-open …, @coreboot forhttps://github.com/oreboot/oreboot
pretty sure we will see lots of critical new software written in C for the bureaucratic reason that ISO 26262 guides exist for C and not Rust. On the other hand, more teams are adopting SPARK. Also, these looks interesting: http://plv.mpi-sws.org/rustbelt/ https://ferrous-systems.com/blog/sealed-rust-the-pitch/ …
Can't argue with that, and I'm glad to see any safer alternative to C being used, be it Rust, SPARK, Go or something else entirely.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
