soham
104 posts
kids, don't avoid frontend.
every TUI, CLI which are user focused, will eventually be eaten by a great GUI product.
less friction wins EVERY FUCKING TIME.
Theo - t3.gg@theo
T3 Code is now available for everyone to use. Fully open source. Built on top of the Codex CLI, so you can bring your existing Codex subscription.
English
the worktree workflow in t3code is far better than the rest of the harnesses, gw goat @jullerino
English
Why is there no content on yt about
- database internals
- compiler internals
- lower level systems stuff in general
I want more deep technical content please somebody make it happen
English
dude, having so much fun vibe coding an entire ocaml stack. hilariously addicting. using quite a bit of cursor cloud agents and it's quite fun w/ some of the long running stuff. also glad i have some credits left over from when we did the tower stuff, haha, i'll be very interested to see what happens with token prices over the next year
English
After years of development - Effect 4 is finally in beta.
This addresses most common painpoints and feedback by making it faster, smaller and simpler.
Effect | TypeScript at Scale@EffectTS_
Effect v4 is in beta. 🚀 Rewritten runtime. Smaller bundles. Unified package system. The most ambitious release we've made so far. Here's what's new. 🧵
English
I hope someday elysia provides first class effect integration.
This framework is too beautiful to pass on.
SaltyAom@saltyAom
@MichaelArnaldi I agree, I hope JavaScript Promise isn’t this bad and if we could have some way out 😭
English
soham retweetledi
@infinterenders love meshing little client islands in a big server component. reduces bundle size, shows static parts ASAP on load etc.
but getting "out of the way" to make a truly client side app means the right primitives are not there for a otherwise goated router framework.
English
yep you can just go with the composition pattern my friend it allows to keep the layout on the server while the "heavy lifting" happens in the client.
it works for fine It keeps your bundle size small by only "hydrating" the Shell, not the static data parts.
the navigation part where people complain a lot it’s simple to manage just lift state above the router
For a truly client-heavy app, the App Router needs to get "out of the way" once the initial page has landed.
English
the brutal truth to the engineer who was always mentioning why we need app router when we had page router
yes pages router are Great . Streaming is what makes the App Router feel different from the Pages Router. It’s not about making the database faster bla bla like that it’s about tricking the user's brain by showing them the UI pieces the millisecond they are ready instantly
English
Big stuff coming for @Tan_Stack very soon on several different fronts. Just when I think I couldn't get more excited!
2026 is going to be nuts. Already is.
English