I see this as an advantage because:
- It's simpler to do that instead of having to do your logic (whether a widget is active, or a function is run) on an external function.
- Performance benefits? (see below)
I see it as a disadvantage because:
- The scripts/styles themselves are in-line, which makes it a bit harder to decipher what scripts are loaded on a page (I know - a bit lazy, but my first go is to look in the header or right before /body for scripts) before using the Network tab in Chrome.
- Not sure how this effects dependencies (if you're loading something inline, yet you have some other script loaded in the footer -- technically your in-line enqueued function is being referenced before the dependency).
- Your script/style loading is done throughout your plugin, instead of one centralized location, which - in the event you have many different scripts/styles, can make it a bit difficult to keep track of everything.
From what I've read on both accounts, it says that scripts/styles (if printed mid-body), are loaded in the footer of the site - which honestly sounds like a performance benefit - but my points above are making this a little hard to decipher if this is just preference, needs to be researched depending on the use-case, or just a lazy/easier way of enqueueing items which while possible - really isn't "the best way to go about this"
I'd appreciate anyone's input so I can hopefully untangle this. Thanks!