RE: Module modularity

[Thijs Schreijer <thijs@...>]

> -----Original Message-----
> From: lua-l-bounces@lists.lua.org [mailto:lua-l-bounces@lists.lua.org] On
> Behalf Of Geoff Leyland
> Sent: donderdag 18 september 2014 4:09
> To: Lua mailing list
> Subject: Re: Module modularity
> 
> On 18/09/2014, at 1:53 pm, Rena <hyperhacker@gmail.com> wrote:
> 
> > Generalize the shared code into a standalone module which those modules
> use?
> 
> Yes, that was the first option above.  I guess I'd just feel a bit silly
> releasing a 100-line module that has no use on its own.  The license and
> readme will be longer than the code.
> 

Difficult to judge. While things are in motion, I tend to keep the code in a separate module. Once they settle and little further development is expected, I merge them so the main modules become standalone.
Only for small modules (100 lines satisfies that imo)

When you publish them as rocks, it's harder, because the standalone version of this small 'useless to almost everyone' module will linger around forever.

Typical for me is that I quite often 'steal' utility stuff from Penlight. In some cases the project grows and more and more code is imported, to the point that I remove it all and call Penlight as a dependency.

I think its personal, but I'm fond of standalone modules. I hate small modules that pull in everything but the kitchen sink.

My 2cts.
Thijs