This looks great in theory but I believe that's where it stops. My main issue is nothing on these slides looks even remotely like JavaScript. My favorite JavaScript feature is all of the many libraries that work together and effect is trying to do it all and I think ultimately makes too many assumptions to be "effect"ive
To me the state of JS is a total mess, the libraries that you say work together really don't and are not though to be, you end up with crappy code that wires them up which will always break, just try to get a basic todo app up and running that has retry logic for calls, error handling, metrics and observability of all procedures, and you'll realise how messy it becomes, in practice not in theory. All Effect ecosystem libraries are based on Effect as a primitive and differently from promises with Effect you have composition for free. We don't make assumptions to be effective, ever, we try to cover as much as possible in a way that the user can model whatever they want
![Noob To Max With DRAGON REWORK In Blox Fruits [FULL MOVIE]](http://i.ytimg.com/vi/LnBMOinoOvA/mqdefault.jpg)
My favorite talk of the effect days! 🤩
You rock, Tim Smart!
Loge to see Tim for real. Also, if the topic is what I think it is, will love to see examples of this feature! Two wins in one
We were also quite surprised to realise that Tim's indeed a real person!
Can we compose something like an optimistic update in that router? How would that work?
Might be a better question for the Effect Discord server to answer as it seems to touch on multiple topics: discord.gg/effect-ts
react-query + @effect/rpc + nextjs when?
This looks great in theory but I believe that's where it stops. My main issue is nothing on these slides looks even remotely like JavaScript. My favorite JavaScript feature is all of the many libraries that work together and effect is trying to do it all and I think ultimately makes too many assumptions to be "effect"ive
To me the state of JS is a total mess, the libraries that you say work together really don't and are not though to be, you end up with crappy code that wires them up which will always break, just try to get a basic todo app up and running that has retry logic for calls, error handling, metrics and observability of all procedures, and you'll realise how messy it becomes, in practice not in theory. All Effect ecosystem libraries are based on Effect as a primitive and differently from promises with Effect you have composition for free. We don't make assumptions to be effective, ever, we try to cover as much as possible in a way that the user can model whatever they want