And let me guess, she paid for the privilege of being forced to stay 5 days and having her baby taken away from her? Unless she’s got amazing insurance?
Honestly, I’m so glad to live somewhere with public health care.
Shine Get
And let me guess, she paid for the privilege of being forced to stay 5 days and having her baby taken away from her? Unless she’s got amazing insurance?
Honestly, I’m so glad to live somewhere with public health care.
Give it to meee
I’m not insisting anything; stating C is not a memory-safe language isn’t a subjective opinion.
Note I’m not even a Rust fan; I still prefer C because it’s what I know. But the kernel isn’t written by a bunch of Lewis Hamiltons; so many patches are from one-time contributors and the kernel continues to get inundated with memory safety bugs that no amount of infrastructure, testing, code review, etc is catching. Linux is written by monkeys with a few Hamiltons doing their best to review everything before merging.
Linus has talked about this repeatedly over the past few years at numerous conferences and there’s a reason he’s integrating Rust drivers and subsystems (and not asking them to fork as you are suggesting) to stop the kernel stagnating and to begin to address the issues like one-off patches that aren’t maintained by their original author and to start squashing the volume of memory corruption bugs that are causing 2/3rds of the kernel’s vulnerabilities.
No idea what you’re being downvoted. Just take a look at all the critical CVSS scored vulnerabilities in the Linux kernel over the past decade. They’re all overwhelmingly due to pitfalls of the C language - they’re rarely architectural issues but instead because some extra fluff wasn’t added to double check the size of an int or a struct etc. Use after frees, out of bounds reads, etc.
These are pretty much wiped out entirely by Rust and caught at compile time (or at runtime with a panic).
The cognitive load of writing safe C, and the volume of extra code it requires, is the problem of C.
You can write safe C, if you know what you’re doing (but as shown by the volume of vulns, even the world’s best C programmers still make slip ups).
Rust forces safe® code without any of the cognitive load of C and without having to go out of your way to learn it and religiously implement it.
This slogan was from the 90s (1993/94 maybe?).
All right, but apart from the sanitation, the medicine, education, wine, public order, irrigation, roads, a fresh water system, and public health, what have the Romans ever done for us?
Well, yeah. Obviously the roads. I mean, the roads go without saying, don’t they? But apart from the sanitation, the aqueducts, and the roads…
What have the Romans ever done for us?
Thanks Satan’s Maggoty Cum Fart.
Having a dog helped me really get to know lots of people in the area when I moved home to somewhere totally new to me. Having a really friendly and safe dog breed makes you immediately so much more approachable, an ice breaker conversation (the dog), and a regular opportunity to meet the same people out and about.
If you’re in a situation where a dog is a good choice, I’d really recommend it.
You can just move the modifier keys around. I have Caps Lock as Ctrl and Ctrl as CMD.
Yeah we’ve been going by primary-secondary where I am for the just 6 to 7 years now but I don’t think a universally agreed replacement for the terms exists yet.
*beating Trump (I assume?)
I’m in leadership at a place where we ship software to hundreds of millions of devices every other week and sure, it sucks to maintain legacy products, but you never sunset something without one hell of a grace period and plenty of warning. And not without feature parity if you’re rewriting to escape tech debt.
There isn’t a valid excuse. They brought this upon themselves and their users knowingly and if they did it without knowing the consequences, that’s even more alarming.
Ship a new app then. Sonos already do this for older products.
Whoever the fuck thought a massive regression for every single customer was the perfect thing to deploy with no option for rollback needs to stop working in software.
Two things come to mind:
Do we need compliance regulations on minimum testing infrastructure etc for kernel-level development so that dangerous bugs can’t be mistakenly released?
Kurtz has a history of this calibre of issue under their leadership (both at CrowdStrike and at McAfee); why does this keep happening under their leadership and what can we learn to instruct other orgs not to make the same mistakes (e.g. via CISA directives)?
If you just want geo coordinates, you could use any open source app and copy+paste them into a note or something.
Nonsense. If they were perfect, wouldn’t they have used a question mark? Your judgement of character is laughable. What empirical evidence is there that they are perfect?
(How was that?)