pip

2K posts

pip banner
pip

pip

@smallboxswe

I launder bits to make money | for the record, I work on query engines

venv Katılım Haziran 2022
1.6K Takip Edilen128 Takipçiler
Sabitlenmiş Tweet
pip
pip@smallboxswe·
I work hard so someone in the office can film a "Day in the life of a Software Engineer" vlog
English
0
0
1
364
pip retweetledi
Mitchell Hashimoto
Mitchell Hashimoto@mitchellh·
This is why RedHat makes like over $6 billion a year by the way. For anyone wondering what the fuck RedHat does, its basically: take the free chips on the side of the road, validate them, and sell the supply chain contract.
English
8
13
407
32.5K
Andrej Karpathy
Andrej Karpathy@karpathy·
Personal update: I've joined Anthropic. I think the next few years at the frontier of LLMs will be especially formative. I am very excited to join the team here and get back to R&D. I remain deeply passionate about education and plan to resume my work on it in time.
English
7.8K
11.1K
147.8K
26.5M
pip
pip@smallboxswe·
meanwhile me who writes c++
GIF
v@iavins

Here is one thing that sucks in Rust and where Zig shines: memory allocation. Let me explain: we take memory allocation for granted, and the language APIs make it look infallible, but it isn’t. Take this: let mut v = Vec::new(); v.push(my_data); The push could fail if the system could not allocate the required memory. In Rust, this straight up aborts/panics. You cannot handle this as an error. Second, you cannot control how memory is allocated, like on the heap, arena, or your custom allocator. All data structures use one global allocator. The current Rust APIs suck. Rust does have an allocator API, but it has been in nightly for many years. Like in the above example, it becomes try_push. Whereas, all of this is first class in Zig. Every collection takes an allocator, and you can pass around the one you want. They return errors which you can handle. In a database, you want to control every aspect of memory. If there is no more free space left to allocate, we want that to become a normal error that can be returned to the caller and handled gracefully. If the database aborts/panics because an allocation failed, that is terrible - one query or one bad allocation path can take down the entire process and affect all connected clients. In Turso, we use a global allocator, and now we are working towards changing that (PR in next tweet). However, we need to add so much boilerplate code, redefine all data structures, and replace existing usage everywhere. It just sucks. This would be so sweet in Zig. A great example is TigerBeetle's codebase.

English
0
0
0
57
Ben Dicken
Ben Dicken@BenjDicken·
@iavins v rewriting turso in zig over the weekend:
English
6
0
65
4.6K
v
v@iavins·
Here is one thing that sucks in Rust and where Zig shines: memory allocation. Let me explain: we take memory allocation for granted, and the language APIs make it look infallible, but it isn’t. Take this: let mut v = Vec::new(); v.push(my_data); The push could fail if the system could not allocate the required memory. In Rust, this straight up aborts/panics. You cannot handle this as an error. Second, you cannot control how memory is allocated, like on the heap, arena, or your custom allocator. All data structures use one global allocator. The current Rust APIs suck. Rust does have an allocator API, but it has been in nightly for many years. Like in the above example, it becomes try_push. Whereas, all of this is first class in Zig. Every collection takes an allocator, and you can pass around the one you want. They return errors which you can handle. In a database, you want to control every aspect of memory. If there is no more free space left to allocate, we want that to become a normal error that can be returned to the caller and handled gracefully. If the database aborts/panics because an allocation failed, that is terrible - one query or one bad allocation path can take down the entire process and affect all connected clients. In Turso, we use a global allocator, and now we are working towards changing that (PR in next tweet). However, we need to add so much boilerplate code, redefine all data structures, and replace existing usage everywhere. It just sucks. This would be so sweet in Zig. A great example is TigerBeetle's codebase.
English
29
30
404
54.6K
pip retweetledi
Ben Dicken
Ben Dicken@BenjDicken·
The essential engineering cheatsheet of 2026: agent → while loop subagent → nested while loop agent harness → the rest of the code cloud agent → all the above, on EC2
English
31
85
989
35.9K
pip
pip@smallboxswe·
@sauravbv so the French toast is just a hype?
English
1
0
1
50
Saurav
Saurav@sauravbv·
Ate some ridiculously overpriced, overhyped sour af mangos with soggy bread ✌️
Saurav tweet mediaSaurav tweet mediaSaurav tweet mediaSaurav tweet media
English
2
0
6
539
pip
pip@smallboxswe·
@raysan5 you use memcpy and expect null terminated string from it? then complain about compilers?
English
0
0
0
67
Ray
Ray@raysan5·
Why C compilers can't agree in how a standard C library function should works? ☹️ And better not to talk about strncpy()...
Ray tweet media
English
107
30
698
241.7K
pip
pip@smallboxswe·
benchmarking sucks
English
0
0
0
17
pip
pip@smallboxswe·
@DebadreeC hope you didn't get beaten up by CRPF or TMC, deba.
English
0
0
1
98
pip
pip@smallboxswe·
"they loop, branch and hold context across steps" - there's already chip for this, it's called cpu
Y Combinator@ycombinator

Inference Chips for Agent Workflows @sdianahu Most AI chips are designed for "prompt in, response out." Agents don't work that way. They loop, branch, and hold context across dozens of steps, and current GPUs hit 30–40% utilization as a result. That gap is where purpose-built silicon wins.

English
0
0
1
99
pip retweetledi
Shivers
Shivers@thinkingshivers·
Past a certain age, a man who's an IC can be a bad thing.
Shivers tweet media
English
43
23
1.7K
408K
pip retweetledi
ᐱ ᑎ ᑐ ᒋ ᕮ ᒍ
ᐱ ᑎ ᑐ ᒋ ᕮ ᒍ@Andr3jH·
"What are you wearing?" "Jensen Huang GTC sweater, sir" "And what is that logo on your cap?" "Palantir, sir. It's a cap from the official Palantir merch store, sir" "What is Jensen Huang's stance on China export controls?" "Soft, sir." "And what is Alex Karp's stance on China export controls?" "Hard, sir" "And you wear a Jensen Huang sweater and a Palantir cap. Is this some sick joke? What is this supposed to mean?" "I think I was trying to suggest something about the duality of the tech bro, sir"
ᐱ ᑎ ᑐ ᒋ ᕮ ᒍ tweet media
English
32
201
3.1K
161.4K
pip retweetledi
Adam Chalmers
Adam Chalmers@adam_chal·
mechanical engineers teaching software engineers about tolerances
Adam Chalmers tweet media
English
29
279
4.8K
276.3K