You'll have to go all-in at some point, there's no other way, which poses its dangers. You now rely on the GH repos/changelogs, their discord for support, etc.
Having worked on a FP-TS app, and with Effect-ts on pet projects, I love the paradigm but I can't help but feel I'm always playing catch-up.
I feel you, we've been hard at work on Effect and the ecosystem these past months (years in fact). Which is why this release and the promise of API stability are such an important milestone. Less catch-up, more shipping from now on!
Evolu (a local-first platform designed for privacy, ease of use, and no vendor lock-in) has been using Effect for many months, and I'm close to releasing a refactoring that will embrace Effect even more (some modules didn't exist when Evolu switched from fp-ts to the Effect).
Effect is a great library, but it has one probably unresolvable issue. Once you use it, you will never want to write TypeScript code without it.
Readit News
You'll have to go all-in at some point, there's no other way, which poses its dangers. You now rely on the GH repos/changelogs, their discord for support, etc.
Having worked on a FP-TS app, and with Effect-ts on pet projects, I love the paradigm but I can't help but feel I'm always playing catch-up.
Effect is a great library, but it has one probably unresolvable issue. Once you use it, you will never want to write TypeScript code without it.
I migrated from fp-ts last September. A learning curve, but Effect appears to be an improvement to Typescript/"standard" way of doing things.
So much that is included out of the box. I am excited about the 3.0 release.
Deleted Comment