Samuel
today in github being a very good and serious website
4 1 53
Samuel
that’s just libertéslop. you only like it because you believe in the rights and dignity of all men
4 60
Samuel
atproto is cool because it is fundamentally pragmatic about what it means to be decentralised. decentralised where it matters, simple and scalable where it doesn’t
4 20 153
Samuel
ask yourself: does this change the power dynamics of the network Y: decentralise it! N: keep it simple!
1 1 30
Samuel
I really am finding that I prefer to use claude to write a very small amount of difficult code than a large amount of easy code
6 5 86
Samuel
just submitted another 2-line PR, so much more fun this way
1 22
Samuel
here’s my harebrained claude system idea: primary agent does a plan->clear->implement loop, to keep context fresh. however, it then forgets things this is where a team of “scholar claudes” come in. they each have a chunk of the full context, review the plans, and chip in with helpful insights
5 1 29
Samuel
the scholar claudes *must* believe themselves to be wearing long scholarly robes, and speak in a dreary tone
3 26
Samuel
when a primary claude finishes their task, they join the scholars, and become the expert on their plan
6
Samuel
do you use git worktrees, or do you use claude in monogamous mode?
10 4 57
Samuel
when I post a draft it doesn't appear in my profile feed... wtf...
5 13
Samuel
lexicon has floats, if you’re brave enough to put every single IEEE754 float in a string field’s `knownValues` array
3 28
Samuel
not for the faint of heart
1
Samuel
don't look at the explore page. nothing is happening there, so you don't need to worry about it. please don't look
11 1 65
Samuel
moving my brain dumping thread here. I think there’s two issues at play w.r.t. perf
Samuel@samuel.fm· 25 Jan
I tried putting it behind useDeferredValue, but it didn't do anything as it seems like the scroll handler has an unstable identity for no good reason
1 4
Samuel
1. List component rerendering. we need to change a scrollview prop on iOS. I already scoped this to iOS-only, so it’s not a perf concern on Android, but it’s got a massive over-render problem. changing this one tiny prop causes every list item to rerender, which is ridiculous
1 2
Samuel
Easy solution - take my existing useScrollsToTop hook, and put a useDeferredValue on it. therefore we can defer this nonsense until after the lightbox has finished rendering alas no. List rerender anyway. Profiler blames onScroll, and I added logging and yeah it changes on that initial ctx change
1 2
Samuel
I’m pretty sure it’s just unstable, I.e. different identity on each render, which shouldn’t be the case - it’s not doing anything here! next step is to narrow down what’s causing it to change. Reanimated has some magical auto-dep-array stuff which is probably to blame - likely doesn’t mesh w/ RC
1 2
Samuel
2. Slow on Android Perf on Android is still unacceptable, especially for 2+ images. I have yet to dig in but I have speculation. the animation gets triggered in a requestAnimationFrame. I’m guessing the main thread is getting locked up so it has to wait a really long time?
2 2
Samuel
Each time each image in the lightbox loads, it re-renders with its image dimensions. So we have 4 fairly heavy components (each image) rendering invisibly before the animation can begin, and each one re-renders as they load. maybe the animation is queued behind that whole process?
1 2
Samuel
what I will try is deferring rendering the other 3 images until after the animation is complete. they’re being prefetched already so it shouldn’t cause any functional changes?
1 1
Older posts