Just curious about the current trend to put client-side templates for single-page Java applications in script tags in your HTML file. Seems like an interesting approach, but is this considered a best practice (or at least a better practice)? I tried to come up with a list of advantages and disadvantages, but the list of bad seems to outweigh the good. 
So the way I see it is this:

Advantages:

1. Only one request to get all templates vs. an individual async request for each template file.

Disadvantages:

1. Creates a potential merge troublespot / bottleneck file if all templates are in one location
2. A bit cumbersome to edit templates all in one file
3. A bit cumbersome to find the template you need vs. using a keyboard shortcut to open file.
4. Have to wait until the DOM is ready before doing anything with a template.

It also seems that with having them in script tags, you can precompile and cache your templates so you're only querying the DOM once to get each template. However, couldn't you achieve the same effect using AMD / Require and a require/text! or dojo/text!? In the latter instance, you'd be lazily loading each template only once. You could then cache it and precompile it at that point.

I just am struggling to see the many advantages of templates in script tags. Am I missing something?