About missing interesting parsers, you are right, for now only the core part is done. Based on community interest, we will work on complementary packages, like more common parsers, easy integration with a web framework like ktor, effectful parsers based on coroutine, etc...
Lots of work ahead :D
The advantage is that you can write code using generics that works with any parser, but I'm a little skeptical about the value of generic code.
In the end, `Parsed` should only be handled whereever you receive the initial input, so the rest of your business logic will be free of it :)
In the end, this is just a tool and it's fine if it isn't fitting your particular style or use case ;)
So if this sort of thing takes off there is likely to be a standardization process at some point.
Go works better for this because common interfaces can be implemented by "coincidence." (Structural types.)