Dreamora is right.
This makes naming conventions a bit awkward. If I have a module that enhances bank functions, I can't call it leadwerks.bank, because that conflicts with brl.bank. I can call it leadwerks.lwbank, so do I give all my modules a "lw" prefix? I have leadwerks.math3D, but if BRL comes out with a math3D module that's going to break mine. Of course, calling everything "leadwerks.lw_" is pretty redundant. Why even bother with separate folders if each module has to be named uniquely?
This makes naming conventions a bit awkward. If I have a module that enhances bank functions, I can't call it leadwerks.bank, because that conflicts with brl.bank. I can call it leadwerks.lwbank, so do I give all my modules a "lw" prefix? I have leadwerks.math3D, but if BRL comes out with a math3D module that's going to break mine. Of course, calling everything "leadwerks.lw_" is pretty redundant. Why even bother with separate folders if each module has to be named uniquely?