News for hackers. Stuff that matters.
Re:Making Sense of React Server Components by paulddraper on Wednesday September 06, 2023 @02:24PM (#37409057)
> and in an ideal world I shouldn't be this granular about it

Hm, could you give an example of this ideal performant state management world? Angular? Vue? Svelte? MobX?

Re:Making Sense of React Server Components by keb_ on Wednesday September 06, 2023 @03:01PM (#37409561)
Svelte is a good example. But you don't have to go that far; Solid and Preact have signals with auto-tracked dependencies.

As another commenter mentioned, yes it's less low level than managing your own dependencies, but then again, most React apps are already wrapped in layers and layers of abstractions/context providers/selectors and use Jest as their test runner (which injects the global namespace with functions) and does other black magic and weird metaprogramming, so I think most React devs are already OK with less lower level stuff.

Re:Making Sense of React Server Components by paulddraper on Wednesday September 06, 2023 @04:06PM (#37410561)
I'm a bit surprised the poster was asking for something more magic not less.
Re:Making Sense of React Server Components by SinParadise on Wednesday September 06, 2023 @10:53PM (#37414196)
I mean, I am OK with magic, but it has to remain magical to me. The moment I have to deal with the magic, I don't want it anymore.