Kishore Neelamegam retweeted
Generational blunder.
At least based on the information that’s available.
NVIDIA announces CEO transition. Read the release: nvidianews.nvidia.com/news/n…
this is the exact issue. only a founder will take risks like this and absorb the pain it comes with
they know that even they blow up, they've started from nothing once and they can do it again
this is why companies die when the founder leaves
Kishore Neelamegam retweeted
Introducing tsrs: a Rust port of the TypeScript compiler 🦀
We are not forking TypeScript!
◆ In close collaborating with the TypeScript team
◆ Up to 8x faster than TS 7.0 & ~70% less memory
◆ Runs in WASM, so it works in your browser & on Workers
◆ Soon part of the Oxc toolchain
npx tsrs
blog.cloudflare.com/typescri…
Kishore Neelamegam retweeted
An uncomfortable truth for a lot of people is that a lot of the most successful people in any industry are wicked smart. We apply stereotypes based on the loudest people, but its not representative of norms. Most are crazy smart and got to where they are because of it.
I grew up in LA, one of my parents was a TV producer, my wife was an actor, many friends "in the industry." I've been constantly surrounded by it, and some of the stupidest seeming people (cause its their bit) are actually insanely smart and strategic in private. It sometimes is just beneficial for various reasons to... not show that side of you.
My favorite anecdote was when a friend (a model) was dating a phD in physics and a very rude person made some off the cuff degrading comment to model friend about it without realizing model friend has their own phD in math lol. You wouldn't know from their instagram though!
For the quoted video, I don't know Ben Affleck. I don't know how deep his knowledge goes. He's almost certainly not going to be more knowledgable than someone who professionally does this area of work full time, but he also to me on the surface sounds like someone who knows a LOT more than the average person and possibly even the average software engineer (on this topic).
Anyways, this applies to tech too. I see it constantly.
Ben Affleck reveals he writes Python, understands convolutional neural networks, worked extensively with GPUs, and used his celebrity status to get private looks at Google and OpenAI’s video models
“I’ve always been kind of into computers since I was young. Then, when film started to move from analog film to digital, I became more interested in that aspect of it. The visual-effects workflow for many years has included machine learning, so I can write pretty shitty Python scripts and stuff like that.
“With convolutional neural networks, which were the precursors to what the transformer can do, which is much more computation simultaneously, you would do things like look at what’s called a tensor. That’s the numerical translation of a visual image in numbers, like the batch number, the frame number and the red, green and blue values of each pixel in each frame. It’s just that simple. That numeric is called a tensor.
“You’d use a convolutional neural network to identify patterns that reveal what’s called edge detection or feature extraction, which is identifying patterns well enough to know, this is where the window ledge is, so we can more easily take the green-screen image out and replace it with something.
“That was familiar to me early on because, prior to Artists Equity, I had a small visual-effects company. I’ve worked with GPUs a lot too. The visual-effects guys said, ‘Hey, you should see. There are a couple: Google and this other company, OpenAI, are doing really interesting stuff with transformers in video.’
“I’ve learned that I can actually just call up and go, ‘Hey, it’s Ben Affleck. Can I come see what you’re doing?’ Sometimes people say yes, to my astonishment.”
Kishore Neelamegam retweeted
Say hello to Rexie, our mascot for Rex! Superlogical public testing is beginning. We’re working through our mailing list in the order people signed up. Initial testing is limited to macOS but that’ll expand quickly. Welcome, new testers. superlogical.com/updates/pub…
Kishore Neelamegam retweeted
introducing 𝚌𝚕𝚎𝚏: our first models trained by @cloudflare's workers ai team.
today, we're releasing two fast and accurate decision models that top the benchmarks for quality and latency. use them hosted on workers ai or grab the weights from @huggingface, because we open-sourced it too.
blog.cloudflare.com/clef-dec…
Kishore Neelamegam retweeted
We are about 3 months away from someone coming clean with this story:
We spent $4m in tokens to port our 2.7m LoC enterprise Java application to Rust.
- P99 performance increased by 0.3%
- RAM usage decreased by 2%
- Full compile times increased by 437x and required 279GB of disk.
- Incremental compile times increased by 9853x and required 279GB of disk.
- Average developer salary increased by 24%
- No one understands the code
- We are super hip again!!
Kishore Neelamegam retweeted
Neki is real and you can try it today!
planetscale.com/blog/introdu…
Kishore Neelamegam retweeted
I can’t stress enough how little an idea matters compared to the agency of the people executing the idea.
I have had the privilege of knowing and sometimes even working with some of the most successful people (by various metrics).
The difference between mediocre and excellent work and outcomes is predominantly one of agency.
In practice this means: they dont wait for things to happen to them they go out and make things happen for them.
They don’t wait for someone else to do something, for someone to teach them, for someone to give them the path, etc. They just go out and find a way to do it.
I think the single biggest superpower these people have is the realization/belief that the world around them is completely mutable. Most everything that happens is because a person made it happen.
I used to tell people to look around the room you’re sitting in. Look at everything. Every noun. It almost all exists because a person willed it into existence. Nothing is stopping you from doing the same.
I see people online all the time dismissing someone else’s success because “I had that idea first” or whatever. I mean… yeah? If so then the difference is… you. So a bit of a self own whenever I hear that.
Number one tip: act with agency.
Kishore Neelamegam retweeted
A lot of people assume @dhh and I worked together before Omarchy, or that I must work at @37signals.
Neither is true.
I just showed up, started pushing PRs, and somewhere along the way, that turned into an incredible friendship.
Ride or die, brother! 🤘 Wouldn’t trade it.
Let me do one serious post chat, and I'll resume shitposting. This is important to make explicitly clear.
Two weeks ago, fellow Dane, David Heinemeier Hansson (@dhh) went on a public tirade about Nix and the Linux ecosystem.
"Goddamn maniacs." "Clowns." "Goblins." "Cancer."
In the same conversation, he called Nix “amazing technology.”
Two days ago, it became clear that he is planning to build his "distribution" on NixOS.
That is worth dwelling on.
NixOS can be criticized. Of course it can. We criticize ourselves constantly.
What I find deeply gross is arriving as a tourist to an ecosystem, using an enormous platform to ridicule the people who built it, then deciding their work is good enough to become the foundation of your own project.
Much of his indictment is not even about NixOS. Land acknowledgements? That is not some defining debate here. It is Twitter culture-war material imported into a caricature of a community he barely knows.
For someone so insistent that technology should be "apolitical", David spends a lot of time talking about politics, culture, codes of conduct, and community governance.
He rails against codes of conduct, then writes rules for how people in his own community should behave while insisting that somehow does not count.
Call it whatever you want. Communities require governance.
And governance, packaging, security, infrastructure, release engineering, review and maintenance are not distractions from building a distribution.
They are the work.
So far, what he has is a configuration and installer layer on top of years of work by Arch, Linux, Rust, and soon NixOS and Nixpkgs contributors.
Using Claude to produce that glue does not make the work underneath disappear.
Packages, infrastructure, security and technical knowledge exist because people did the difficult, boring work required to make this ecosystem function.
You are not replacing those people. You are depending on them.
Which makes the rhetoric about creating a home for the "competent" people obnoxious.
David, the competent people are already here.
They are the people your project depends on — including people and communities you have been calling clowns.
You do not get to praise the "amazing technology", dismiss the people who sustain it as politically deranged, put a layer on top, and cast yourself as the serious technical adult in the room.
That is not escaping dysfunction. It is standing on other people's work while sneering downward.
People mock NixOS. They declare it insane. They explain why nobody should want it.
And then they use it anyway. So who's competent here?
You can hate us. You can mock us. You can call us clowns.
But when the answer to your own technical problems is to build on our work, that tells its own story.
So, David: welcome to NixOS.
But understand what you are standing on.
If you intend to build on years of work from this community, the attitude adjustment is overdue: less culture-war posturing, more respect and humility toward the people doing the work you now depend on.
Kishore Neelamegam retweeted
🎉🎉🎉Boom
@nvidia joined the Rust Foundation !!!!!!
Kishore Neelamegam retweeted
One of the most surprising parts of building @pgrustdb for me and @JasonSeibel has been how effective formal verification is. We've been using Kani to do so.
With Kani, we've proven that thousands of functions in pgrust behave exactly the same as their C counterparts
Kishore Neelamegam retweeted
🎉 CUDA Rust is here! Team 🟩 ❤️ 🦀
You can now write CUDA kernels in plain Rust, two ways: cuda-oxide (SIMT) and cutile-rs (Tile).
developer.nvidia.com/blog/in…
Kishore Neelamegam retweeted
We've been aggressively fuzz-testing @pgrustdb vs. Postgres. For individual functions, we'll generate millions of inputs to find any behavioral differences between the Postgres and pgrust versions.
In the process, we've found over 20 different bugs in Postgres itself
Kishore Neelamegam retweeted
6 months ago, most of Bun’s PRs came from people prompting Claude
Nowadays, most of Bun’s PRs come from Claude prompting Claude
A weird experiment I've been trying the last few weeks is having Claude take over day-to-day maintenance of our apps. Seeing early signs of life that this might be possible.
The setup is straightforward: we have a Slack channel called proj-claude-maintains-apps. In it, Claude Tag runs a bunch of daily routines across iOS, Android, Desktop, web, CLI, and Agent SDK:
- Crash fuzzer: open the app in a simulator and tap around to find ways to crash it, then root cause and fix the crashes
- Dup unifier: scans the codebase for similar-yet-slightly-divergent abstractions, and puts up PRs to unify them
- Dead-code remover: removes statically unreachable code, and adds logging to suspected dead code to check if it's really dead and if so, remove it the next day
- Abstraction police: fixes leaky abstractions
- a bunch more..
Results have been surprisingly positive. Over the last few weeks, these routines have opened 388 PRs across our repos, 180 of which we merged after Claude Code Review + human review. We're now thinking about how to streamline this to make merging these kinds of mechanical changes easier.
Claude generally gets these PRs right on the first shot, and if it doesn't, we ask Claude to tune its routines so it's better the next day. Sometimes it takes a few days of tuning.
To try a similar workflow, ask Claude Code or Tag, or create some routines directly at claude.ai/code/routines. A few of the actual prompts I used below.
Has anyone experimented with similar workflows?
Kishore Neelamegam retweeted
We're making Git hosting more reliable, performant, and scalable.
This post traces 20 years of Git infrastructure and explains how that history led us to design and operate our Git storage, Origin, as if it were a database.
cursor.com/blog/git-at-any-s…
Kishore Neelamegam retweeted
pgrust is 300x faster than Postgres on analytics. 10x of that comes from our column format, pgrcolumnar. With it, we read 1/10th the data Postgres needs to answer an analytical query. We designed pgrcolumnar so types have the same on-disk representation as they do in Postgres


























