i'm on [@atwork.place]( )! [atwork.place/u/danabra.mov]( ) https://morel.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:fpruhuo22xkm5o7ttr2ktxdo&cid=bafkreieyievr5tobqrlf37afog4ey7foxjlan5ncdgj2lgawi4ho5tgh2a
is lexgen supposed to be fussy about which lexicons it is given? i'm seeing generated code seemingly broken because i haven't explicitly downloaded some com.atproto lexicons https://morel.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:fpruhuo22xkm5o7ttr2ktxdo&cid=bafkreiaj2urnuynyb5vons4z5ktp2xvfnzfdfbelpzxiboej7sugktlca4
is jsr: worth the pain? every time i see a package using it i get slightly annoyed because it doesn't seem to be natively supported by npm, and so it gets in the way.
the [@slices.network]( ) "just hit the API for which we have a dashboard" model of building AT apps feels so much more comfortable than rawdogging ingestion and sync. i'm looking at the simplest vanilla statusphere example, and the entire `appview` folder (oauth, sync, db) reads like a liability 😭
the [@react.dev]( ) Compiler works for the same reason that compilers for pure programming languages are able to make non-trivial optimizations. if your code is composed of pure functions, it is safe to re-order their computation, or save the result for some inputs and reuse it for later for same inputs.
i thought [@ricky.fm]( ) talk was very good. i hope they’ll glue it up together from two days into a cohesive video. slightly sad about the last example breaking (a one-line mistake) but such is the nature of live demos. overall i think it’s a great conclusion to last ten years of work from the team. πŸ’œ
i agree, not because i hate ai or think its bad or whatever, but because it looks ass. it rarely communicates more than prompt. semantically it’s like 2x2 resolution, waste of space RE: View quoted note β†’
this is actually my motivation for typelex. not so much specific production usage but more that i can't write an atproto tutorial that includes "write this json blob". i *still* want to close a tab when i see a lexicon json definition. so with myself as the "target reader", i *need* an idl already RE:
very interesting talk by [@lunaleaps.bsky.social]( ) from the second day of react conf about RN threading and virtualizating lists, highly recommend watching https://morel.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:fpruhuo22xkm5o7ttr2ktxdo&cid=bafkreihddbjeg65wvhyjw2ltxexjs6ra4pf4mbqib733uqv3eb2btkeqpe
the biggest challenge in contributing to the AT ecosystem so far is whatever small project i think of doing, i find out somebody has already done before. this isn’t a complaint though i wish things were more discoverable. but also i just need better ideas