Hi,
I have just stumbled upon this library and read the documentation homepage with great interest. The insight on the downsides of fp-ts (stacktraces, esm compatibility) and comparison with effect have been interesting to read. Having started new projects with fp-ts and avoiding effects it was interesting to see some attempt of continuation of fp-ts.
Now I see that the last activity in this repository happened 2 years ago. I am curious to hear the reason for this. Are you still using fp-tx but do not have any needs to extend it or have you moved on? In the latter case, why and what are you using instead? Do you no longer recommend fp-ts these days for new projects? I am curious to hear how your understanding and conclusions might have shifted.
Thanks!
Hi,
I have just stumbled upon this library and read the documentation homepage with great interest. The insight on the downsides of fp-ts (stacktraces, esm compatibility) and comparison with effect have been interesting to read. Having started new projects with fp-ts and avoiding effects it was interesting to see some attempt of continuation of fp-ts.
Now I see that the last activity in this repository happened 2 years ago. I am curious to hear the reason for this. Are you still using fp-tx but do not have any needs to extend it or have you moved on? In the latter case, why and what are you using instead? Do you no longer recommend fp-ts these days for new projects? I am curious to hear how your understanding and conclusions might have shifted.
Thanks!