Hot take: Reactivity, as it currently exists in JavaScript frontends, is a nice idea, but can't be executed properly with what JavaScript currently is as a language.
Frameworks that try to work around these limitations always have edge cases that don't fully work, and they depend on a lot of slow behind-the-scenes magic to do their job. Non-trivial things also quickly become too hard for devs to build correctly.
As long as reactivity isn't a first-class citizen in JS, it's not worth doing.
@scy I have the opposite hot take: For me, declarative programming / reactivity is the only thing worth doing for UI, even if language support is lackluster (for JavaScript mostly because Proxies still don't support wrapping primitive values).
@leah Ooooohhh, thanks! It's great to see that they're indeed working on that.
I'm not sure whether I agree with all of their design decisions, but then again, I've only skimmed the proposal.
For example, in my mind I was imagining it as being able to subscribe to changes to any value, not just to those wrapped in something specific. Sure, that would be a rather big language extension.
Also, I'm not happy that the design is explicitly targeting "frameworks, not vanilla JS devs". But hey.
Add comment