Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think it’s totally fair. I discourage redux and all related patterns for this very reason. Well that, and I think local state is actually a good thing (and moving state out into separate files a bad thing).

To me the proxy object (or proxy class) is really the best abstraction - much like valtio. Or a compiler like svelte.

There’s no reason for ducks, epics, sagas, etc etc. We have a programming language already, we should use it.



It sounds like you're agreeing with me. You don't need everything up front, so listing everything is a bit disingenuous.

It's the same explaining a fully kitted out backend (Routing, caching, authentication, etc) and then going "see, it's so complicated!". Well duh, it's a big and complex system.

I think the issue with valtio is that there's no central store. As far as I can see, you'll end up having these proxies scattered around your codebase or you'll end up re-creating Redux and centralizing them.

Also, I have ironically never heard of valtio.


Agreeing how? By using valtio you avoid needing to know most of that list, by using redux you.. don't.

Also, you can easily wrap valtio with:

  const createStore = (name, store) => {
    if (window.stores[name]) throw 'store already exists'
    window.stores = {
       ...window.stores
       [name]: valtio(store)
    }
  }
And boom, you can see every store just like redux.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: