are there any cheap alternatives to react-native-svg? i don’t like that its draw shows up in every frame in a significant way. always thought “svg in react native” is too good to be true, and apparently it is RE:
hmm we should make actor autocomplete work after "from:" operator
til you can "unprecompute" things https://morel.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:fpruhuo22xkm5o7ttr2ktxdo&cid=bafkreihdlfwfqi6p6z6hkrrydma47icvmgvl3yu6qwemzva5lmjmjwfpym
i can almost hear it https://morel.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:fpruhuo22xkm5o7ttr2ktxdo&cid=bafkreihsjo33drxp65giyrv53ds52mh6uootbbtmm5lcabcyrzsrep3cui
test [Twitch]( )
another W for open source RE:
lets ride
woah fantastic thread, thank you so much! lots to dig into RE:
still trying to chase down Android choppy feed scrolling. added some instrumentation to the app — using React profiling builds and to track long render phases. we *do* have long tasks (presumably rendering offscreen story items as you scroll) but they’re on the JS thread. so why stutter? https://morel.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:fpruhuo22xkm5o7ttr2ktxdo&cid=bafkreigqz4hohtphce5gy26nkrubkzil6yg5bkmhy53j2426rkssirsmie
it sucks that findNodeHandle does completely different things (performance-wise) depending on what you pass to it. for class instances, it does an expensive traversal searching the tree for the “current” version of the double buffered fiber data structure. for native views, it’s O(1) property read