A modern programming language that makes developers happier.

kotlinlang

easiest setup is to have :core for common stuff, features that depends on :core, and top level :app which depends on all features

probably depends on the size, right? I can imagine that on a small project `core` will have multiple packages and once you scale, those semantic packages become separate common modules.

(one note, this whole setup will need adjustments for dynamic features, but thankfully it's a rare animal)

or maybe instead “semantic packages become separate common modules” you will get too many code that too hard to separate later