Pretty proud about this one.
This stacked drawer menu solves one of the biggest issues of menus: multiple levels.
You can basically add as many levels as you want and everything will work out of the box.
I've been saying that Dynamic Workers really unlocks a whole new branch of the tech tree, enabling things that just weren't possible before, and this is such a good example. more like this please.
State Machine design pattern is widely used in game development for this exact reason , its makes composing really complex animaiton sequences into easy to build blocks
Depth-aware light injection in TypeGPU
I got a 448x448 monocular depth model down to ~8 ms on my M4 Pro across ~250 dispatches, which is fast enough to use in realtime :D
Since the inference is written directly in TypeGPU, I can just feed the depth buffer straight into the lighting pass. It never has to leave the GPU or go through any extra synchronization/interop step
Inference, lighting and draw all go through the same command encoder.
An Indian engineer in Bengaluru got tired of potholes destroying his car.
So he built an app with Codex that detects them, finds who is responsible, and files a complaint.
Here is how it works. He installed a dashcam with GPS and an accelerometer. The app records everything while he drives.
A vision model classifies every pothole by size. Small, medium, large.
But here is the clever part. Most Indian roads are under warranty.
The contractor who built them is legally responsible for fixing potholes for free.
His app searches through 2,900 government contracts, finds the exact tender number, identifies the officer responsible, attaches the photo and geolocation, and generates a ready-to-file complaint.
One drive to work. 12 potholes detected. 12 complaints ready.
--
vc: @gkcs_
The engineering team just hired a new lead developer who came from a major Silicon Valley firm.
He scheduled a 1-on-1 meeting with me to review our core database architecture.
He opened his laptop and pointed out that all of our enterprise user data was routing to a single, monolithic Excel file on a local drive.
He said it was the most horrific thing he had ever seen in his 15-year professional career.
He asked me why a Fortune 500 company was running its entire infrastructure off a spreadsheet from 2014.
I didn't even blink.
I told him we don't use standard relational databases because they're inherently vulnerable to SQL injection.
I explained that our architecture is a proprietary flat-file hyper-matrix.
I said it completely bypasses traditional query language, making it virtually invisible to foreign state hackers.
He stared at me for a long time and said the file was constantly crashing because it had 4 million rows.
I told him the crashes were actually automated micro-reboots designed to clear the cache and maintain system latency.
I used the phrase "kinetic data obfuscation."
He started sweating and asked how we handle concurrent write requests from 50 different sales reps.
I told him we enforce a strict single-thread chronological bottleneck to ensure absolute data purity.
That just means whoever clicks save last overwrites everything everyone else did.
He looked like he was going to have a panic attack right there in the conference room.
He asked if we had any plans to migrate the data to AWS or Azure.
I told him the cloud is just a computer owned by someone else, and I don't surrender corporate sovereignty to third parties.
He resigned the next morning citing irreconcilable technical differences.
I had HR classify his departure as a failure to adapt to our culture.
Launching Copper, a Mac app for capturing things you want to keep and prompts you want to try next while working with AI.
The more I use AI, the more I find myself collecting little things I don't want to lose.
You're in ChatGPT and think, "I'll need this later," but you don't want to stop what you're doing. Then you're in Claude. Cursor. Chrome. Back to ChatGPT.
Before long, you've got little things scattered everywhere. An answer you want to keep. A link. An idea. Or three follow-up prompts before the current one has even finished generating.
I had this problem, so I built Copper.
Copper combines the useful parts of a to-do list, a clipboard, and a scratchpad. It's built specifically for AI-assisted work. It sits next to where you work and is always one shortcut away. It works with all your AI apps, terminals and browsers.
Whenever I find something worth keeping, I capture it. If I think of a few prompts while the AI is still responding, I type them into Copper. Then I send them back into ChatGPT, Claude, or Cursor and check them off as I go.
Copper is local and private. It doesn't sync anything, doesn't collect anything, and doesn't need an account.
I've used Copper every day for the past few months. It has completely changed how I work.
If this feels like something you'd use, it's $39. One-time purchase.
React Aria is now available in shadcn/ui.
Use `--base aria` or choose React Aria in shadcn/create.
All components, docs, CLI, styles and skills have been updated for React Aria Components.
Shoutout to @devongovett who did most of the work behind this release.
I am excited to announce that we are officially writing a new version of Postgres. In Rust - and creating the LLVM of databases in the process.
In the span of a year, we have rewritten SQLite. Keeping the compatibility, increasing its feature set. MVCC, Types, (Live) Materialized Views, among other things. In the process of doing that, we have realized: At the end of the day, what makes SQLite special is that it compiles SQL to a database-specific bytecode. So why can't we compile *Postgres* to the same bytecode?
Turns out we can. I ran an experiment called pgmicro as a way to prove this hypothesis, and it works very well. It is time to make this official, and put the weight of Turso behind it. We shall give the world a modern take on Postgres. Wire compatible, but built on a new architecture.
We have already heard of others wanting to extend this. MySQL? Redis? the sky is the limit. What can we do if we do for databases what LLVM did for compilers? To prove how powerful the SQLite bytecode is, we are actually running DOOM compiled to the unmodified SQLite instruction set. And because Turso runs natively in the browser, you can play the game in your browser. With the database executing it.
Read the full story below! 👇