Straw-people love to say that #rustlang is terrible for quick-and-dirty scripting tasks: just write Python or Perl!
My experience with it has been great though: CLIs are so smooth to write, there's great crates for all the dumb little things you want to do, and path + string processing is super easy. And then you can actually read / modify the script in the future. We've been working on a generate-release script for @bevy with multiple contributors over the last month; it's been lovely.
oct can now set up cards in #KDF mode, the text output format was improved for readability, and some minor bugs were fixed.
Finally, version 0.11.0 uses #rPGP, a pure #Rust OpenPGP library 🦀.
As a result, the binary on #Linux links to four fewer dynamic libraries, while at the same time being 10% smaller.
Hi! It's time for this week's edition of the #bevymergetrain. If this is your first time here, every week a do a round up of the community-reviewed PRs for @bevy, the #opensource#rustlang engine for #gamedev that it's now my full-time job to help maintain!
There's a whopping 20 PRs ready this week; let's check in on and each of them and I'll make the final call:
This week in the Bevy ecosystem we see Tiny Glade ship a Steam demo, live VJ sets powered by Bevy, screen space reflections in the deferred renderer and more.
We've also got the usual showcases and a couple really interesting crate release for 2d lighting systems and gpu particles.
Ja und Nein, denn Rust ist im grunde sicherer aber auch das kommt darauf an wie mensch es umsetzt. Ich vertraue Rust mehr als anderes Coding, ich schau mir die Libs-Daten an.
»Speichersicherheit – Fast 20 Prozent aller Rust-Pakete sind potenziell unsicher:
Nach Angaben der Rust Foundation verwendet etwa jedes fünfte Rust-Paket das Unsafe-Keyword. Meistens werden dadurch Code oder Bibliotheken von Drittanbietern aufgerufen.«
Expand glob imports is an underrated feature of Rust Analyzer. It’s amazing how the black box melts away when you understand what your framework is bringing into scope.
I think there would be still space for systems programming language with a constraint from day zero that it would 1:1 compatible with plain C”s binary layout and memory model:
Roughly just .text, .bss, .rodata and ,data.
No symbol mangling at all.
All the memory safety etc. fancy features would be then designed within exactly those constraints.
#Rust is essentially a derivative of C++ when compiled to binary, which does not really make it a strong competitor for plain #C. It can substitute C in many cases for sure, just like C++ did, but there’s always need for minimal systems programming language, which also looks elegant in binary, not just in source code.
A compiled C program can be quite easily understood with a binary with no debug symbols at all if you understand the CPU architecture well enough. That is, and will be a strong asset for C.
I'm doing a lot of Blender -> Bevy work at the moment, and I needed a way to visually check the resulting texture atlases. Hence this sprite viewer that pulls in the metadata I'm generating via python scripts and Blender.
bevy_inspector_egui on a Resource + the generated information and I can check the animation for any directionality and any animation.
It's often good if secrets are redacted in logs: This avoids accidental publication of a user PIN (or decrypted payload) in bug reports.
On the other hand, it can be useful for a developer to have full and verbatim logs (including secrets) for debugging.
We started work on this, but would like to hear from you. What should we do?
I wrote an overview and sales pitch for #RustLang for my new website: https://www.ncameron.org/rust/ What do you reckon? Does it tell you what you'd need to know if you're curious about Rust, but don't know much about it?