3 ms·
> I think that it's an unachievable ideal. There are two approach: batteries included and community driven. You know, there might be a somewhat nice middle gro
by wtetzner 6y ago
> I think that it's an unachievable ideal. There are two approach: batteries included and community driven.
You know, there might be a somewhat nice middle ground: after several community driven libraries have materialized, maybe include some interfaces in the standard library, that allow users to choose which community library the want without having to hardcode too much to that library.
It's not perfect and wouldn't work for every situation, but might be a way to soften the downsides of the community-driven approach.
- ernst_klim 6y agoWell many OCaml libraries do abstract from Lwt/Async using Functors allowing you to choose library you want to go with. But it's still not perfect since sometimes third party libraries still need to write concrete implementation of something diving into lower level, hence breaking the abstraction. This "interface" approach wouldn't work in all cases.
- pdimitar 6y ago> after several community driven libraries have materialized, maybe include some interfaces in the standard library, that allow users to choose which community library the want without having to hardcode too much to that library. That's what Elixir did with calendars and timezones. Worked great.