> Just to be clear I think Bluefin is really cool and I'm a fan of your work overall.
Thanks!
> I'm speaking from the industry/production perspective here. When polysemy and freer-effects were released there was a similar belief that they were here to stay.
Well, from my perspective, I've never worked at a place that's used polysemy of freer-effects.
> transformers and MTL have stood the test of time, are heavily documented, and are pervasive throughout Hackage. Understanding them and how to build programs with them is essential for anyone trying to break into 'production haskell' as a career move.
> Well, from my perspective, I've never worked at a place that's used polysemy of freer-effects.
I have with another deprecated effect library. Its a bummer to have something so core to the architecture that is deprecated but then to not have the time or buy-in to do anything about it.
That does sound like a bummer. To add some explanation, to explain why I said that effectful and Bluefin are here to say, it's because they're based on IO, so it's easy to get them to interoperate, and if in the future a new "EffectSystemX" comes along, also based on IO, then they will interoperate with that too. Thus the risk of them being deprecated is minimal.
I haven't published my effectful-Bluefin interoperation layer, but you can see it here:
Thanks!
> I'm speaking from the industry/production perspective here. When polysemy and freer-effects were released there was a similar belief that they were here to stay.
Well, from my perspective, I've never worked at a place that's used polysemy of freer-effects.
> transformers and MTL have stood the test of time, are heavily documented, and are pervasive throughout Hackage. Understanding them and how to build programs with them is essential for anyone trying to break into 'production haskell' as a career move.
Sadly true.