fp-ts and effect-ts

[shinzui]

Hi,

I am confused about the announcement of fp-ts joining the effect-ts ecosystem. Can someone please clarify the implication of the announcement on fp-ts, io-ts, and monocle-ts?

[gcanti]

All new developments will happen under the effect org, roughly speaking there are the following correspondencies:

• fp-ts = effect/data + effect/io
• io-ts = effect/schema
• monocle-ts = fp-ts/optic (not yet accepted into the effect org)

When possible, some of the features designed and implemented in the effect/* packages will be backported to fp-ts in order to

• make easier switching to effect
• make fp-ts better for users who don't want or can't switch to effect

[p3tr2005]

thanks, dude. now i don't have to switch into effect cause i like the fp-ts so much.

[shinzui]

@gcanti Thank you for answering. I'm one of the users who don't want to switch to effect, so it's reassuring that fp-ts will not be only in maintenance mode.

[nandin-borjigin]

There is one more package @effect/typeclass which has the typeclasses using v3 HKT.

[albertodiazdorado]

@gcanti If we are using fp-ts, should we migrate our projects to effect-ts? Is there any timeline (or deadline) for the migration?

[gcanti]

"should"? not at all, it's only worth migrating to effect-ts if the benefits it offers outweigh the costs of migration

[albertodiazdorado]

Oh perfect, that's great!

I had (mis)understood that fp-ts was on the way to being discontinued (as in "We backport bugfxix in Node20 to Node16, but eventually Node16 will no longer be supported" ). Thanks for the clarification :)