🔥The 9th Round of Easy Loan, Earn $40 Reward is in progress❗️ ⏰ Promotion Period: January 15th - Feburary 15th, 2025 👉 Register now and check more details at gate.io/campaigns/358

takeTheBait redd.it/1l6z63r

A null pointer caused the Google outage yesterday. No mention of memory safe alternatives🤔

We need to get rid of the billion dollar mistake (null) before it becomes a trillion dollar mistake

How is this a good thing? This is how CVEs happen

Easy-to-change code is high quality. Hard-to-change code is low quality.

Ask me anything about Fil-C (my spare-time project to make a compatible and memory safe implementation of C and C++).

”The image loaders written in Rust are usually on-par with, & sometimes even faster than, their C/Assembly counterparts, while only using memory safe code. In practical tests, we did find considerable speed improvements, especially for JPEG & PNG images.” blogs.gnome.org/sophieh/2025/0…

bzip2 officially switching from C to Rust. Not only is Rust a nicer language for the implementation, and not only is it safer, but the Rust implementation is also *faster* than the C implementation... C-niles will have to up their doses of copium. trifectatech.org/blog/bzip2-cra…

Impressive flex from the University of Utah: Augmented Vertex Block Descent (AVBD) «Vertex Block Descent is a fast physics-based simulation method that is unconditionally stable, highly parallelizable, and capable of converging to the implicit Euler solution»

Stricter aliasing rules, even with almost identical code, will give you a speedup, btw. Rust is faster than C

beAGoodDev redd.it/1ldkfgu

I’ve always considered formal methods to be a grandiose aspiration that’s disconnected from reality. - No commercial company can afford to spend time formally verifying components - verified components don’t guarantee any attributes for the system as a whole - “faster and

Creator of FilC try not to be disingenuous challenge (IMPOSSIBLE) libbzip2-rs doesn't actually aim to remove all unsafe, it's literally just a cleaned up c2rust implementation. A manual one would have way less `unsafe` (or even none at all, yeah). it's also ~10% faster than the

This is a horribly disingenuous take (removing unsafe from the automated transformation hasn't even been a goal yet), & it ignores that the Fil-C implementation is waaay slower than the original C, while the rust translation is *faster* than the C implementation.

this is what cultists are getting paid to shill Rust

"How productive are your developers?" or "How easy is it for your developers to do the right thing?" I bet you've been part of teams that measure productivity with ticket counts, burndown charts, or lines of code, but productivity in software is about feedback, flow, and focus.