This article is amazing! While implementing a binary search may be considered elementary (Introduction to Algorithms Chapter 2), but writing a truly efficient and reliable one is challenging, especially when you factor in branch prediction.
This article nails it with a real-world example that kept me engaged from start to finish. Even though I have little experience on the topic, I thoroughly enjoyed reading it and learned a lot.
RT @phptek
Get ready for a unique and informative talk at #PHPTek 2023! @enunomaduro will be presenting "Rust For PHP Developers." Don't miss out – register now at https://tek.phparch.com#php#rust
Underappreciated are the curly brackets for delimiting lexical blocks, and the semicolons required for separating statements. Others, like #Java, might seem old-fashioned, yet here's a language from the 2010s adopting conservative syntax.
It removes confusion for the compiler, AND for people reading the code, being easy to type due to IDEs. Like in natural language, punctuation is not clutter.
「 Microsoft is rewriting core Windows libraries in the Rust programming language, and the more memory-safe code is already reaching developers.
David "dwizzle" Weston, director of OS security for Windows, announced the arrival of Rust in the operating system's kernel at BlueHat IL 2023 in Tel Aviv, Israel, last month 」
I’ve been watching out for languages that could encroach on JavaScript’s power domain (the browser) for awhile. Since Node, it’s been able to play on other language’s turf, but not the other way around.
The idea that #rust could compete with #javascript on its home turf is one that I’ve watched carefully. The blocker seemed to be WASM bindings; that is, JS was still fastest at working the DOM.
"#Microsoft is rewriting core #Windows libraries in the #Rust programming language, and the more memory-safe code is already reaching developers.
David 'dwizzle' Weston, director of OS security for Windows, announced the arrival of Rust in the operating system's kernel at BlueHat IL 2023 in Tel Aviv, Israel, last month." https://www.theregister.com/2023/04/27/microsoft_windows_rust/
For now i will be focusing on my YT channel full time. I have many ideas for it and now that i'm free i can dedicate all my attention to showing the creative side of programming, just as i wish it had been shown to me.
I'll be doing more #rust, #kernel hacking, NVMe and SSD work and, of course, animation and art for my videos. Who knows where it'll lead?
I'll be honored if you tag along with me on this adventure. I think we'll build some pretty things.
@janriemer thanks 😊️. Indeed results can vary based on distance of rows and growth state of the crop, but field trials have shown promising results with up to 60% savings in herbicides. One technical aspect to note in addition: yes it runs on #Rust code 😉️
Last week i run a poll asking how comfortable people are with "?" in #Rust. That sent me down the rabbit hole of Try/FromResidual.
So, i made a video about it. If you want to understand exactly what "?" does to Result, or a practical example of how to use Try types, give this one a look:
"The focus of my research is applying #fp, in particular #chez#scheme, to low-level problems — the type of situations that usually call for #rust or #c"
— highly recommended talk on programming with serialized data from @vollmerm @ #ELSconf
Looks like a world first to me 🚀 New functionality developed as part of collaboration between @activetraveleng and @turinginst 🔥 #opensource contributions welcome 🙏👇
So I have a few thoughts on why Haskell is not more popular.
Haskell sort of dropped the ball by not being more user friendly. This is not about "keeping Haskell simple" - I like the fancy types and advanced features in Haskell and I wish it would get more such features - this is specifically about the community and the new user onboarding experience and how to fix it.
On today's internet exploration I came across a fun little Doom maps project with a very nice writeup. Poked around some of the other blog posts and I love the presentation style!
#Rust and #Nix has this thing in common, people excited about them manage to drag it in to every discussion, and will derail it to talk about their pet thing talking down at others and just kill the good discussion that was there.
I have some improvements and fixes for the sysinfo crate that I've been wanted to do for weeks but can't find the time for it... T_T
One of them I discovered thanks to @slomo is that some C functions could error with "EINTR", which means you should call it again and not return with an error. The more you know...
Are there any #llvm contributors/reviewers on here? I'm making some changes to improve Windows (CodeView) debug info and would love for someone to have a look. First change is here: https://reviews.llvm.org/D148761 #rust#clang