I can see why layTheme and layGridder are different products with different purpose. This is why i'm a customer of both. But some things that could benefit to both are sometimes only developped for one and it is often layGridder's loss.
Module CROSS Compatibility
We can create our custom modules for layGridder and this is awesome. But cross-compatibility could really empower this feature. Because layGridder has a small userbase compared to layTheme, there is very little incentive into creating custom modules plugins. With cross-compatiblity, layTheme could see "modules extension plugins", layGridder would see more of them.
This is very important and already fixed in layTheme (which actually needs it less).
- layGridder is using fixed sizes
sizes="(min-width: 701px) 89.9vw, 100vw"
- layTheme is using
Because layGridder is a plugin, we're supposed to be able to set any width we want for the gridder. But if we do, the fixed sizes in the attribute will be false (to calculate the fixed sizes, layGridder always consider the gridder is 100vw large).
So the gridder on my website is 60vw large and still downloading 4k images which are four times more heavy than necessary.
Last week I brought up the fact that layGridder is making invalid HTML while layTheme doesn't.
I had no anwser on the original post but this is kind of important for a plugin :
If i'm using a smooth scroller (pretty basic) going through id="iamtheone" then "iamthesecond", "thethird", etc.
If i'm on the page will never scroll for me. Because it is scrolling through the invisible id="" from the hidden desktop layout. That's just an exemple not even my own usecase.
VW vs %
Like srcset="" it is also an issue on a gridder that wouldn't be 100% of the viewport width.
I'm also bringing this back to life. Precents % are better than VW where it can be applied (it's better everywhere but especially in layGridder where the developper may want to use a custom width for the gridder).