Nathan Helmig

@FirstSquawk Everyone is "dumping" treasuries. Oil is 100+ a barrel. It's traded in dollars. How do you think they get those dollars in a hurry.

CHINA IS DUMPING U.S. TREASURIES, WITH HOLDINGS FALLING TO THEIR LOWEST LEVEL SINCE THE GLOBAL FINANCIAL CRISIS.

@dvassallo Oh ur definitely a bot

@NateHelmig You don’t have to do any of those things. Nothing was taken away from us. We just have more options to program faster.

Programming was never free if you wanted it done fast. You hired people. Now you buy tokens.

@jarredsumner Please put in the blog post why the bun is so much smaller and faster in rust!? I don't think that is something you can take at face value.

Still writing blog post hopefully will post tomorrow

Wait a minute. So the rust rewrite is smaller by quite a bit and faster? That does not give you pause? Do you know why? Will it be in the blog post? I'm sure you have at least a theory and not taking it at face value? I also think the zig team would be very interested in knowing why! It's probably really valuable information and would be the due diligence I think bun kinda owes to the language.

I have yet to see a benchmark where it is slower than the Zig implementation. It is basically the same codebase. It doesn’t use async rust and like the Zig implementation, uses few 3rd party libraries. It’s really the same thing just with better tools for us to prevent crashes.

Bun v1.3.14 releases tomorrow. If we do merge the Rust rewrite, this would be the last version in Zig

@filicroval @kimmonismus 2-3million "+". Whatever that's surprising to mean

@filicroval @kimmonismus Ya but how much did the researcher cost to prompt and work with the model. Never talk about that do they.

Three researchers used Anthropic's Mythos to build a working macOS kernel exploit that bypasses Apple's M5 Memory Integrity Enforcement, a security system Apple spent five years and billions of dollars building. Bug found April 25. Working exploit May 1. Walked into Apple Park to deliver the report in person. MIE was the flagship security feature of the M5 and A19, designed to kill the entire memory corruption bug class. According to Apple's own research, it disrupted every known public exploit chain against modern iOS. Calif didn't break MIE. They walked around it. Data-only attack, no pointer manipulation, standard syscalls from an unprivileged user to root. The 55-page technical report drops after Apple patches. This is the story of the year in cybersecurity.

@filicroval @kimmonismus And there were three researchers. We are talking probably 2-3million

@dhh did omarchy get pawned? Why was the most recent update pointed to omarchy 4 alpha?

@mitchellh This^

It isn't unexpected that the focus of the Bun Rust rewrite is on the anti-Zig side more than anything, since the internet loves to hate. What is unexpected and unfortunate is that leadership within Bun hasn't tried to steer the conversation away from that at all. There are so many positive and interesting takeaways from this and I'm not really seeing any of them pushed as the primary message. A positive thing that hasn't been talked about at all is how far Bun came thanks to Zig. And even if you dump it now, its meaningful for how good Zig was to even build a product to this point and impact by any metric. I would've loved to see anyone in leadership say this. On the interesting side is how fungible programming languages are nowadays. Programming languages used to be LOCK IN, and they're increasingly not so. You think the Bun rewrite in Rust is good for Rust? Bun has shown they can be in probably any language they want in roughly a week or two. Rust is expendable. Its useful until its not then it can be thrown out. That's interesting! There's been a lot of talk about memory safety and no doubt Rust provides more guarantees than Zig. But I'd love to see a better analysis of why Bun in particular suffered so much rather than take the language-blame path. How could engineering as a practice been more rigorous to prevent this? What were the largest sources of crashes other programs should watch out for? How does Rust prevent them? How could Zig theoretically prevent them? That's interesting. I know the official blog post hasn't come out yet from Bun. But they're smart enough to know that that PR would stir up controversy the moment it opened, or they should've been. And plenty in the company have been tweeting and writing about it. Its somewhat telling to me in various dimensions what they chose to talk about first. I tend to think I'm pretty good at corporate PR/comms (especially when it comes to developer audiences) and I think appealing to the negative is never the right long term strategy; it does work to get short term eyes though.

Henry Ford didn't pay his factory workers well and kept them employed out of the goodness of his heart. It was pragmatism and out of fear for his business. He gave his workers the ability to buy the vehicles they made. Money wasn't being lost via wages it was recycled. He would get the best out of them because his employees and their families would not go hungry. For it was satisfaction that keeps every great business's greatest fear at bay. A hungry competitor with a better cheaper product and a jaded and starving work force willing to build it for him. It is people that make a business not some board or a bot. Degrade your business. Outsource your labor. Do it. The next great business is waiting.

Amazon, $AMZN, has announced another round of layoffs in its selling partner services division after cutting nearly 30,000 jobs in recent months.

Not knowing/controlling the bounds of your input/output size, timing, and allocations is saying hey computer please on random machine please break on my user in unexpected and unfortunate ways that make my life and theirs miserable. If you don't set the boundaries in which your program can break and how your users system will.

@rfleury In a general-purpose program like a compiler, which could take a very large amount of input, how can you ever know that you've reserved enough address space for your heap/arena thing? I feel like you always need to allocate another range if it fills up.

"The stack" is a per-thread address space range, dynamically reserved by a kernel when a thread is created. The reason why "stack" is often presented as preferable to "heap" is that, when using a thread's stack, the expensive part of allocation - address space reservation, and preparation of physical pages for backing the address space - has already been performed when the thread was created. But kernels also provide mechanisms for doing your own address space reservation (mmap, VirtualAlloc), and there is nothing stopping you from using these to do bulk allocations up-front to create your own stacks. This can make common case allocations as cheap as "the stack", but the advantage is that you now control the semantics and lifetime of the stack you've created. Thus, it does not need to be coupled to - for example - the lifetime of a scope or function, as the thread stack is. The "stack versus heap" dichotomy is an unfortunate mythology because it seems to, in practice, communicate the idea that when a thread stack is insufficient for some purpose (allocations must exceed scope boundaries, allocations may need to exceed thread stack limits, allocations require more fine-tuned reserve/commit behavior, and so on), then the only alternative is the heap, particularly for very granular allocations. This is, again, a mythology, and it has confused the C++ world in particular for decades.

@ThePrimeagen If just one anthropic employee would pull down the pi-mono repo and read it then just go make exactly that in C with memory arenas they would have the best harness.

The team that has members doing +200 commits a day? Bro, I don't even think they know how to fix claude code

@jarredsumner You basically want @jonhoo

My team is hiring to make Bun and Claude Code faster. Runtime internals, epoll/kqueue, parsers, JS engine work, long-running agent loop perf. Years of production C/C++/Rust required. $320k - $485k salary. SF in-person. job-boards.greenhouse.io/anthropic/jobs…

@jarredsumner ALSO WHY DOES EXPERIENCE MATTER!? YOU HAVE CLAUDE MYTHOS!? YOUR COMPANY IS NOT BEING CONSISTENT!!!

@jarredsumner Lol who has years of c/c++/rust/ and agent loops... Agent loops have only been around for a couple of years. You got some hr/LinkedIn recruiter writing your tweets?

@Figure_robot why do these robotics companies insist it should look like people? why wouldn't you just make it a claw crane like hand that just moves shit around.

Watch a team of humanoid robots running a full 8-hr shift at human performance levels. This is fully autonomous running Helix-02 x.com/i/broadcasts/1…

@unusual_whales meaningless even if it gets made into law. majority of them are wealthy.

BREAKING: The Senate has passed a resolution that would withhold lawmakers’ pay if the government shuts down.

@mitsuhiko x.com/mitsuhiko/stat… saying this and then saying your killing dependencies for "reasons" is wild... go std lib batteries included btw

Killing dependencies in pi. Because reasons.

ya it would only be faster and more memory efficient out of the box. faster start up... better C bridge with cgo(this is super important) Even with a whole lua interpreter embedded into it for plugins... written in a language that was built for real thoughtful concurrency/parallel execution... it would probably be smaller in memory footprint than pi(every mb counts when running local ai now). ya definitely no advantages...

Pi wouldn’t make any sense in rust or go. Extensibility is key to it. That leaves ruby, python, js, php for the most part unless you want to ship an interpreter. None of those languages have any benefit over node.