An apt observation Katy made about #Rust: It was clever of them to call crates crates, but you don't generally put creates into packages. They should've called them pallets.
#rust
ALPHV (BlackCat) is the first professional ransomware gang to use Rust
Security researchers have discovered this week the first professional ransomware strain that was coded in the Rust programming language and was deployed against companies in real-world attacks.
It's a first of some sort at least.
I'm not sure it matters too much neither for the victims nor the analysts what programming language the malware authors used though.
More #rust musings: I'm given to understand that the hardest thing to wrap one's head around is ownership. Having needed to deal with manual memory management in C/C++ in the 90s, this just seems like the compiler doing automatic sanity checking on my code. I can see why it would be hard for someone who's always just relied on a garbage collection before though.
Impressions on #rust so far: It's basically like if C were re-imagined from the ground up without having to worry about backward compatibility.
20 Things I’ve Learned in my 20 Years as a #Software #Engineer
source: https://www.simplethread.com/20-things-ive-learned-in-my-20-years-as-a-software-engineer/
“How can you not know what #BGP is?” “You’ve never heard of #Rust?” Most of us have heard these kinds of statements, probably too often. The reason many of us love software is because we are lifelong learners, and in software no matter which direction you look, there are wide vistas of knowledge going off in every direction and expanding by the day. This means that you can spend decades in your career, and still have a huge knowledge gap compared to someone who has also spent decades in a seemingly similar role. The sooner you realize this, the sooner you can start to shed your imposter syndrome and instead delight in learning from and teaching others.
...
https://www.youtube.com/watch?v=zefaQgPqqac
#developer #programmer #coder #nerd #geek #economy #work #knowledge #project #management #wisdom
Labour concerns with conditions at Rust production where Halyna Hutchins died
I heard of the Rust film production firearms mishap early today. Following details of current Hollywood productions isn't my metier, but the filming had come up in a conversation between Alex Baldwin and Bob Garfield (of Bully Pulpit) recently.
The context brought the headline into sharper focus for me.
Details of the incident are beginning to emerge. Among them, a labour action in which numerous production members had walked off the site. The film, for which Baldwin is producer, continued regardless.
Alec Baldwin ‘Rust’ camera crew walked off the set in protest before the fatal shooting
Hours before actor Alec Baldwin fatally shot a cinematographer on the New Mexico set of “Rust” with a prop gun, a half-dozen camera crew workers walked off the set to protest working conditions.
The camera operators and their assistants were frustrated by the conditions surrounding the low-budget film, including complaints of long hours and getting their paychecks, according to three people familiar with the matter who were not authorized to comment.
The camera crew showed up for work as expected at 6:30 a.m. Thursday and began gathering up their gear and personal belongings to leave, one knowledgeable crew member told the Los Angeles Times. ...
The prospect that corners were cut, risks were made, crew were fatigued, and as a consequence one life was lost and another put in severe jeopardy, seems increasingly likely.
#HalynaHutchins #AlexBaldwin #Rust #Risk #Hollywood #FilmProduction #Shootings #Accidents #NewMexico #SantaFe
A "Stream-What-You-Hear" implementation written in Rust.
It's a great little tool that I use to stream audio from my PC to my #DLNA
https://github.com/dheijl/swyh-rs
I've been playing with low level stuff on my computer in #Rust, and it is amazing how dumb so much of it is. Every time you turn on your computer, it's like… If you walked out into your driveway and there was a 1921 Model T, and to drive anywhere, it would transform itself into a 1931 Model A Ford, then a 1964 Ford Mustang, and then transform itself into a 1986 Ford Escort, and finally into a 2021 Ford Escape Hybrid. And the reason why? Well… what if someone wants to listen to AM radio? We have to maintain backwards compatibility to the Model T in case anyone wants to listen to AM radio. But the modern car can have an AM radio without having to transform itself from a Model T!? Yeah, it could, and in fact it does do that. There's no trace of the original AM radio in the Escape, but, I d'know, that's just the way it's done.
Every time I get excited about something I see... it's the #Rust people. The Rust people seem to be doing all the exciting things, to me. It seems to me that GNU/Linux might be getting a little old, and it's starting to get compromised, or so it feels to me. I know other people sort of feel this.
DevC - Linus Torvalds "Nothing better than C"
[video width=”492″ height=”426″ mp4=”https://dwaves.de/wp-content/uploads/2021/08/Linus-Torvalds-Nothing-better-than-C.mp4″\]\[/video\]
what is great about C?
- - the simplicity of the compiler that just run’s anywhere
- still THE most resource efficient language
- with C the user does not have to buy a new computer every 3 years, because of updates slowing down the system so much it become inefficient
- still THE language that can speak best to hardware
- the syntax can be called ugly sometimes, but not as ugly as C++ X-D
- still THE most resource efficient language
everyone understands what this does:
cat boolstd.c
#include
#include
int main(void) {
// set to true
bool b1 = 1;
// this is correct, it will print
if(b1)
{
printf("Bool b1 is true \n");
}
// set to false
_Bool b2 = 2;
// this is false, will not print
if(b2 == false)
{
printf("Bool b2 is false \n");
}
// requires
bool b3 = true;
// this is correct, it will print
if(b3 == true)
{
printf("Bool b3 is true \n");
}
// requires
bool b4 = false;
if(b4 == false)
{
printf("Bool b4 is false \n");
}
}
the problems of C:
- security problems need to be adressed (all those buffer over- and underruns)
… security/safety plus multi core computing is what RUST tries to adress
RUST the safer C/C++?
#linux #gnu #gnulinux #opensource #administration #sysops #dev #devrust #rust #devc #c #linus
Originally posted at: https://dwaves.de/2021/08/19/devc-linus-torvalds-nothing-better-than-c/
A quand réécriture du code source du noyau Linux en Rust ?
Le noyau Linux est écrit en C. Or le langage C manque de fonctionnalité de haut-niveau, ce qui rend le développement plus complexe qu’il ne serait avec un langage de haut-niveau.
Et Rust est justement un langage de haut-niveau qui est beaucoup moins enclin à tolérer des erreurs de code qui peuvent être préjudiciables (sécurité…).
En effet, le langage Rust se concentre sur la gestion sûre de la mémoire, permet une gestion automatique de la mémoire et fournit les moyens d'atteindre un parallélisme élevé de l'exécution des tâches.
De son côté, Google a déjà annoncé sa participation à une initiative visant à promouvoir le support de Rust dans le noyau Linux et a fourni les aspects techniques de la faisabilité de la mise en œuvre de Rust pour lutter contre les problèmes découlant des erreurs de travail avec la mémoire.
Google estime que Rust est prêt à rejoindre le langage C pour le développement des composants du noyau Linux.
D'ailleurs, Google founi comme exemple, l'utilisation du langage Rust pour le développement de pilotes de noyau, et ce, dans le contexte de leur utilisation dans la plateforme Android (### Rust est reconnu comme un langage officiellement supporté pour le développement d'Android).
