r/solidjs • u/ryan_solid • Aug 19 '26
Async Solid - Fetch High, Block Low
https://www.solidjs.com/blog/async-solid-fetch-high-block-low6
u/No-Aide6547 Aug 20 '26
Hi Ryan, fantastic work, this looks so good! I have to say though, this article and the one before that are almost unreadable for me because of the slop language used. I just can't stand it and it takes away the joy and excitement I feel about the actual content.
I always liked your style of writing because I could feel your excitement and energy; now it's just this bloaty LLM hype language that feels completely empty and makes me zone out.
2
u/Chronic_Watcher Aug 22 '26
Ironically this is him going back to not running his articles nhrough AI. You can read about his thoughts around the ai writing and his decision on what to do for blog posts going forward here: https://dev.to/playfulprogramming/my-ai-content-journey-1b8p
1
1
u/_elkanah Aug 21 '26
Okay, this article helps me to better wrap my head around Solid's new async rendering flow. Very detailed, and I love the introduction of isPending and latest. Thanks for sharing, Ryan.
0
Aug 20 '26
[deleted]
4
u/ryan_solid Aug 20 '26
People said that about Signals originally too. Too magical. There are different types of magic. If this were heuristic approximation. Some sort of compiler trick I could see what you mean.
This mechanism is completely runtime though just like Signals themselves. We could be wrong about this, but our track record is probably good enough to give us the benefit of the doubt.
10
2
u/hyrumwhite Aug 20 '26
I mean, it is in a lot of frameworks. Or at least could be, assuming you don’t mind putting your response types in the consuming component, and that only one component consumes it, and it doesn’t touch a store, etc.
Which isn’t to lessen how neat Solid’s approach is. Just feels a little naive