It is hard to understand why one would want to introduce this into their codebase given how functional javascript is right away. It lives in the spectrum of rxjs - super powerful, but is it necessary? Can all of those concepts be distilled down into what you would use on the day to day (just a few), with less concept density, and just as much functional goodness?
I was skeptical but have come to find it indispensable. I absolutely love it for exhaustive handling of states and corresponding typed errors, schemas, and managing concurrency. It’s possible with other tools, but Effect offers much more than just that. It’s a lot of fun. There’s a learning curve, but once it clicks it’s pretty intuitive. It’s simpler than it looks.
It has truly led to shipping more robust programs that are easier to debug. I don’t use it everywhere, but I don’t think twice with larger backend projects.
sibeliuss · · focus · HN ↗
steve_adams_86 · · focus · HN ↗
It has truly led to shipping more robust programs that are easier to debug. I don’t use it everywhere, but I don’t think twice with larger backend projects.