Built fun things at @X, Sometimes take photos. All (many) opinions are mine.
Tel Aviv / SF
Joined August 2007
- Tweets5.2K
- Following3.7K
- Followers2.1K
- Likes123K
Such a fun concept from one of my favorite oss contributors
There’s no reason to not have a website anymore…
I can finally say — after 9 years! — here’s mine:
lukeed.com
1
2
658
Me: “NO NEED for a rollout plan, it’s not in production yet”
Opus: “I’ve created a 314 fully recoverable migration plan, 15 versioned api endpoints and two run books”
Somewhere in the @Boeing HQ, a bunch of engineers are reading this and having the best day ever.
Can we get it on IMAX??? I just want to FEEL the entire room shaking. Best pre movie trailer ever.
3
13
699
AGI is here
Also AGI: "I'm going to duplicate this rust build 10K time and fill up your 4tb disk"
lol
1
13
1,197
The English version of the letter shared by LVMH leader. Superb writing and an amazing use of this platform.
3
3
1,243
I love this app
It was an honor to visit your husband’s grave today on your behalf, and to pay my respects. It was wonderful to see the beautiful flowers representing many others who did the same. Our nation owes a debt of gratitude to those who made the ultimate sacrifice, and to the loved ones they left behind. Thank you for your service and sacrifice @SharrellAnne2 🙏🏽
2
3
1,578
DuckDB is super useful, and this is an incredible addition to its massive set of capabilities
We are happy to release DuckLake v1.0, a production-ready lakehouse format specification. Its reference implementation, the ducklake DuckDB extension, is available as of today in DuckDB v1.5.2.
Since releasing the DuckLake manifesto in May 2025, we have seen massive adoption, with DuckLake deployed in production at multiple organizations, third-party clients supporting DuckLake, and even an upcoming O'Reilly book. DuckLake v1.0 ships many new features (inlining, partitioning, bucketing, type system improvements) and guarantees backwards-compatibility in the specification.
2
4
1,308
lol Golda Meir (first Israeli woman prime minister, the one she’s so badly misquoting) rolls so hard in her grave that we connected her to a generator and solved all of Europe power issues.
What a world.
I keep telling people that if Israel laid down its arms, there would be peace tomorrow. If Iran laid down their arms, they would wiped from the face of the planet.
Or something.
1
3
441
Took me a second to work this out because I’m stupid, but in case you’re wondering these are Hezbollah rockets launching.
As they launch, there’s a literal Laser (Iron Beam, you can’t see it) exploding them in flight. xitter-newx.xyz-mikolabs.workers.dev/kann_news/status/20282…
1
398
Congrats to the amazing team behind @bunjavascript
Anthropic is acquiring @bunjavascript to further accelerate Claude Code’s growth.
We're delighted that Bun—which has dramatically improved the JavaScript and TypeScript developer experience—is joining us to make Claude Code even better.
Read more: anthropic.com/news/anthropic…
3
944
OK, been asked to write a bit on why this is a bad idea.
There are some performance issues that i'm going to ignore at the moment, but focus on what I think makes the web amazing, which is the *stateless nature* of it.
Why stateless? why is it important?
- *every* HTTP request that is sent from the client to the server, has *everything* that is need for the request to complete.
- This means that the server *doesn't have* to keep a state attached to every user / request (it can chose to though)
- This also means that different servers (versions of the software, locations, and actual machines) can handle your request *transparently* and without any coordination with any previous server that served you in the past
- This also means that rolling upgrades, A/B tests, load balancing, proxying and many other techniques are also extremely simple, as you don't have to "transfer the state" from a different server to continue serving the request
- Error handling and failures can be solved by client retries which is so much simpler than having a complex way of serializing state.
- For the vast majority of the web (like going through wikipedia, e commerce or IMDB) this is absolutely amazing and simple
- For many SPAs or complex apps, this is also quite good, moving complexity to the client instead of the server (which is much easier to scale)
- HTTP has a lot of other benefits, like built in caching standards, authentication, a metadata system (headers) and many other things you'll have to build yourself if you build on websockets.
Websockets are also awesome, if used well, but they do present some annoying production issues (yay rolling upgrades)
I don’t know if @charliekirk11 even knew how many people around the world his logic, common sense and values have touched and encouraged.
We lost a great man, who embodied free and open debate.
RIP.
