Deprecation Notice: replaced by CE3 #175
Description
TL;DR: if you use this project for anything serious (I doubt it), this is the time to speak up! After the first version of CE3 is released, this project will be published one last time against CE2 and archived immediately.
We should probably start thinking about a future with Cats Effect 3.
First of all, I don't think many production applications are using console4cats, because console output will (or should) usually be made using a logger, which Console isn't. So in my mind, our major users are CLI tool authors and developers debugging some code quickly. Everyone who needs console output in a library probably rolls their own implementation too.
Cats Effect 3 brings cats.effect.std.Console and a IO.println, so I think most (if not all) of console4cats becomes redundant. We also should not be publishing a cats.effect.Console type in my opinion, as it's not really our namespace.
My suggestion for the post-CE3 world would be to not have a compatible release and ask users to switch to cats-effect-std's native Console and IO.println instead. After some time, this repository could be archived (or maybe we can do it just after CE3's release).
Because (assuming my assumptions are correct) the scope of breakage is limited (to CLI tool authors, and there aren't that many tools built with CE [that I know of]), I would say it will be a quick migration anyway.
What do you think?
Activity