Lita 조원경

@amadeus Nice!!!! Congrats!!

Weeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee

If you've been wondering what I've been up to, the team and I have been cooking up something new. A new agent-native development environment deeply integrated with the GitHub graph. Not just for writing code, but all of the meta-work as well.

@pierrecomputer i hope those speakers made it to the video

What do you think is cooking in the Pierre office today?

@sarahwooders Pieeeerre!!

Is anyone building github for agents? Specifically: - API/SDK interface - make millions of repos no problem - fast

@sqs @united Not a long flight, but flying out from SFO -> SEA on Sunday. User is lita

The final boss of an interactive client<->server application is intermittent airplane wifi. Amp worked pretty smoothly for me on a 15-hour SFO-SYD @united flight, but we want to make it buttery smooth. If you have a flight in the next 10 days and want to help us test, reply here with your Amp username and flight route, and I'll send $250 in free credits. You then just need to post your feedback using Amp in flight. Would also love a photo of Amp in flight, and a comparison to how other agents work in flight. (I'll have Amp decide for me which of the replies seem legit. I reserve the right to not pick everyone.)

@thorstenball @sqs Syncing all this state sounds hard. Excited to give Neo a try.

This is one of the most elaborate distributed systems I've personally worked on. And, fun fact: we built it twice. Multiple weeks on one platform only to realize the platform won't work. Then I rewrote the core in one weekend to another platform. Then hardening it there.

Also, when a customer states your product gave you another 9, no better endorsement. This was Cursor btw, and how they use temporal for their cloud agents product.

Achieving six 9s is an impressive feat. No wonder temporal has the reputation of being reliable.

If you have a project that needs fast, reliable, git based code storage that is built with modern, agentic workflows in mind then we should have a chat about code[dot]storage DM here or email kris[at]pierre[dot]co

@Golden_Bearz I approve of Tina fey being Berkeley. Timothy is piedmont, let’s be real here

Berkeley // Oakland // Walnut Creek

@isaacinthesky You are too kind Issac 😭 but you also had an impressive network stack stripe !! So your opinion has merit on its own!

@litacho says lita cho, former staff engineer at lyft (the home of envoy proxy)

i do take anurag's point here, and it makes sense, but a _load balancer_ is among the strongest possible places to think about a rewrite in in zig/rust

@rakyll The more abstraction and frameworks you add, you trade off some sort of performance as no abstraction/framework is going to be a perfect solution for your context unless you built it yourself.

@rakyll Preach. Also because go builds so fast, I have fast feedback loops to test. But concurrency is going to be hard.

Go provides lightweight threads and a variety of synchronization capabilities as core language features for convenience and a unified library space. Go never claimed that concurrency is easy.

@ahmetb Shutting down cleanly is tricky to get right and I always write it gross during the first pass.

if you enjoy using the concurrency primitives in Go, challenge yourself to implement a connection pool sometime. there are A LOT more edge cases in this than I originally thought.

@ahmetb @haileyhmt Be change you want to be, Ahmet

@haileyhmt this is how i wanna be using linkedin but i guess im too scared

we need more ppl like kevin

I thought I provide a counterpoint of what Tauri provides, as we migrated our Electron app to Tauri. As with any technology, everything is just full of tradeoffs. Since Tauri has a rust core, locks, threads, shared runtime memory, and os calls are much more performant than javascript/typescript. We heavily leverage concurreny, as we read and write to files on disk. Using a system language is going to be far more performant when manipliating a filesystem. Tauri is also inherently secure out of the box. Tauri explicitly requires you to grant permissions for the filesystem, network, etc., and lets you scope resources. With Electron, you do have to open a port to communicate with the Node.js runtime, which might be a feature for some people. Tauri uses native bridges and function closures between the webview and Rust core, which is inherently safer than local-network IPC (you can encrypt data between the network calls, but you pay for that in performance) as the data never leaves the runtime. Also, using the OS webview, your app benefits when users update their OS, and the binary is smaller because you do not have to package Chromium separately. But the real reason we migrated: native libraries. Using libgit2 via FFI and jj-lib natively is worth the tradeoff of WebKit bugs. We pass an OAuth2 token at runtime and run git push / git clone under the user's own credentials. Yes, we do face painful WebKit bugs, especially around rendering the text cursor. But we thought that the cross-platform bugs were worth the trade-off of the security benefits. I do believe that you can make an Electron app just as secure by using service workers and iframes. It is more work, and you do give up performance for it. But you can do it. If you want to go deeper, I gave a talk at Git Merge: youtube.com/watch?v=4UVzX3… that covers our migration in more detail.

@fat I want one!! Next SF visit??

Sometimes we make hats