I already raised this topic some time ago about Ar...
# arrow
g
I already raised this topic some time ago about Arrow modularisation. Core size is definitely important thing especially for beginners (who don’t want to bring huge library with a ton of things that you not sure how and where to use). But currently Arrow modules based on layers, core/data/syntax/typeclasses Maybe make sense to use feature-based modularisation (or Data Types based), same as it worked on FunKTionale. I think it’s fine to have Effects and Optics as separate modules but what about having different data types (or a few related) in a separate module together with syntax? I don’t have any specific plan, I just not familiar enough with source code and you vision of this. But I see that Funktionale approach worked for me and very granular. Maybe you don’t want to have too many modules, but you can combine multiple modules to layer using additional artefact.