Gian::Lu﹤🦀﹥ retweeted
lads... LADS...
we have never been more back than at this very moment, right here, right now, as you read this
Gian::Lu﹤🦀﹥ retweeted
OpenAI is Ditching TypeScript to Rebuild Codex CLI with Rust 🦀
#rust #rustlang #programming
analyticsindiamag.com/global…
Gian::Lu﹤🦀﹥ retweeted
[1/*] If we take the chance that a tool (compiler, linker, batch, whatever) remains working for a particular codebase after one year as a given probability p, then the chance that build remains working after x years is p^xn, where n is the number of tools used in the build.
Gian::Lu﹤🦀﹥ retweeted
Haskell doesn't make I/O difficult; it reveals that I/O is difficult.
Rust doesn't make manual memory management difficult; it reveals that manual memory management is difficult.
One time Dijkstra was accused of making programming more difficult and responded that he was only revealing how difficult programming is.
nitter.gq/AlgebraFact/status/192…
Gian::Lu﹤🦀﹥ retweeted
"Rewrite in Rust" is widely used because of their own interest. (It happens in other new languages also)
But Most of the people ask others to rewrite either new to Rust or rage baiting others to hate Rust devs
Gian::Lu﹤🦀﹥ retweeted
"if I throw enough fish at a tree one of them will climb it and see the world" - @Caedrel
Gian::Lu﹤🦀﹥ retweeted
The clue is in the name, type alias. Meaning the type is still the same. We use type aliases to reduce having to type redundant things, such as aliasing away the Err type in a Result.
Use newtype pattern if you want two types out of one type
Gian::Lu﹤🦀﹥ retweeted
I think you should read more before blaming languages. In the original post, you wrongly compared with Go is type feature instead of type alias.
The Type "alias" is mainly to reduce the boilerplate not to create new types the same as Go
Gian::Lu﹤🦀﹥ retweeted
When you split a function to N different small functions, the reader also suffers multiple "instruction cache" misses (similar to CPU when executing it). They need to jump around the code base to continue reading. Big linear functions are fine. Code should read like a book.
Considering function size in isolation leads to fake and wrong conclusions. Anyone who puts forth a general rule like this is revealing something.
Consider, if you split a lot of your functions into 3 functions each, what burden is added in terms of understanding the program?
If you combine a bunch of tiny functions into bigger ones, what burden is removed?
Gian::Lu﹤🦀﹥ retweeted
Welcome to the Red Bull family @Caedrel 🐀👑
Gian::Lu﹤🦀﹥ retweeted
and it shows!
Microsoft CEO says up to 30% of the company's code was written by AI | TechCrunch techcrunch.com/2025/04/29/mi…
Gian::Lu﹤🦀﹥ retweeted
WhatsApp is using Ratatui for their new Erlang crashdump viewer! 🔥
🚀 Supports memory address decoding & more!
🦀 Written in Rust & built with @ratatui_rs
⭐ GitHub: github.com/WhatsApp/crashdum…
#rustlang #ratatui #tui #crashdump #erlang #logs #whatsapp #commandline #terminal
Gian::Lu﹤🦀﹥ retweeted
Rocal UI is a simple Rust template engine for building views. It uses familiar syntax for embedding variables, if-else logic and loops. #DEVCommunity #RustLang
dev.to/picolt/rocal-ui-a-sim…
Gian::Lu﹤🦀﹥ retweeted
New Git diff alternative just dropped! 🔥
🎸 riff — A diff filter highlighting which line parts have changed.
💯 Supports highlighting conflict markers, merge commits & more!
🦀 Written in Rust!
⭐ GitHub: github.com/walles/riff
#rustlang #git #diff #highlight #commandline #vcs #development #programming #terminal
Gian::Lu﹤🦀﹥ retweeted
DAY - 23
@LosRatoneslol - ONE PIECE
See if you guys can tell who is who 😂 Drawing one piece was surprisingly fun xdd Also thank you Caedrel for keeping the rats 😎
