12 ms·
agreed. the problem with these AMD frameworks is that the asynchronous nature and deeply nested callbacks are almost completely unnecessary because you end up c
by jongleberry 14y ago
agreed. the problem with these AMD frameworks is that the asynchronous nature and deeply nested callbacks are almost completely unnecessary because you end up concatenating/minifying the assets before production anyways. You end up with unreadable files. With synchronous CommonJS frameworks, most of this nesting is eliminated.
- reissbaker 14y agoWith AMD you generally only have one (in a rare case, two) levels of indentation added on top. I much prefer CommonJS too, but deep nesting's not really a fair accusation.
- jongleberry 14y agotrue. i'm being a little sarcastic, but 1-2 levels of _unnecessary_ indentation bothers me when it's easily avoidable.
- reissbaker 14y agoFair enough. Aesthetic reasons aren't the worst ones in the world. It's also just so... Yeesh. Complicated, in comparison.
- slurgfest 14y agoDo you find that this is a big deal in practice, or does it just feel messy to you?
- jongleberry 14y agoit's more like it's unnecessarily messy, which bothers me. if it was necessary, then it wouldn't bother me. and it's not just the nesting that is messy, the whole `define` stuff going on is messy.