i'm highly enjoying using railway.app
i think instead of starting with serverless, it would be good for many developers to start with Railway and then try serverless. i feel a lot more comfortable understanding the tradeoffs now
Railway
ah too bad "use cache" still includes Build ID as one of the keys which defeats the purpose for me (i want the cache to survive deploys). i take it there's no way to work around (if i commit to stability myself) other than patching...
some pieces i thought are interesting:
- e2e-ish queries and actions tests: tangled.org/danabra.mov/...
- rsc-friendly data layer tangled.org/danabra.mov/...
- redit "use cache" handler (this is entirely claude so idk if it's correct) tangled.org/danabra.mov/...
lexicons tangled.org/danabra.mov/...
i've never written a fullstack app before so let me know if i got something wrong :) this was very much coauthored by Claude but i did a lot of steering and can sign off on maybe 90%
cool news, sidetrail.app is now open source on @tangled.org@bsky.brid.gy!
the stack:
- atproto (jetstream + new lex client)
- next 16 + cacheComponents (yes, a recent version)
- postgres + drizzle, redis
- vitest
danabra.mov/sidetrail
ehh idk how i feel about liquid glass (just upgraded). i donβt hate it, but is there any particular app that really show it off? maybe i expected it to be more disruptive somehow
people reporting being unable to tap buttons on ios, can anyone reliably reproduce this? i'll update my phone to ios 26 i guess but i haven't been able to repro so far
View quoted note β