I have much respect for Effect.ts, and indeed there’s a conceptual overlap between it and what I’m doing in Emmett; the difference is that I prefer not to fight with the language and keep things simple and accessible. Having said that, I’m not a big fan of Effect, as it requires a lot of mental heavy lifting from newcomers.
Out of curiosity, Jacob, what do you enjoy about Effect the most?
Totally understand! There's a litany of ways to make a mess and only a handful of ways to make something that someone else might find intuitive, just like anything else haha.
What I enjoy the most about Effect is how easy it becomes to establish an error channel that's both type-safe and compositional. I didn't really have to change my style of coding all that much (once I was done climbing the learning curve). I still found this to be true with your code snippets from the article; it was cool to play around with them. I can show you if you'd like!
Given how much thought you’ve put into this article, you’d probably love Effect-TS! Definitely worth the learning curve.
I have much respect for Effect.ts, and indeed there’s a conceptual overlap between it and what I’m doing in Emmett; the difference is that I prefer not to fight with the language and keep things simple and accessible. Having said that, I’m not a big fan of Effect, as it requires a lot of mental heavy lifting from newcomers.
Out of curiosity, Jacob, what do you enjoy about Effect the most?
Totally understand! There's a litany of ways to make a mess and only a handful of ways to make something that someone else might find intuitive, just like anything else haha.
What I enjoy the most about Effect is how easy it becomes to establish an error channel that's both type-safe and compositional. I didn't really have to change my style of coding all that much (once I was done climbing the learning curve). I still found this to be true with your code snippets from the article; it was cool to play around with them. I can show you if you'd like!