I politely disagree with ending up with more boilerplate code with marionette... you're ending up with _less_ boilerplate code when using marionette with backbone, and even when including marionette, your "boilerplate" code is necessary configuration... binding dom elements, events, template handling, rendering, data serialization... even more so if you're doing it in CoffeeScript.
behold... a view in 3 lines of code.
class Views.AlbumTracks extends Marionette.CompositeView
className: 'album-tracks'
template: 'album-tracks'
behold... a view in 3 lines of code.