I don't know much about this but here are my 2 cents.
It all depends on what "that matter" means. When it comes to SEO, if scripts on the head result in lower site rating then it doesn't matter if the scripts are blocking or not, that is just how SEO likes them. (I'm talking about SEO because Sardor mentioned it but I don't know much about it).
Now, if what you mean with "that matter" is blocking or non-blocking JS then what you're talking about HTML5 is correct. However, the advantage of having the <script> tags at the bottom comes from a different perspective which basically is: "Load the HTML and CSS first and then load the behaviour". That way, the user can see something (eg: upvote/downvote buttons) and while the user interprets the rendered page and moves the pointer to the action he/she wants to perform then usually JS files have already been downloaded and executed. If the user was faster than the download and execution of the JS files then the action will not take place.
So to summarize, there is a tradeoff on having the script tags on the head and at the end of the body and, IMO, it fully depends on what the JS files do (adding behavior to components or styling) and the server's performance (having script tags on the head on slow servers might result in pages frozen displaying no content for some milliseconds/seconds).
PS: I've seen an attempt to turn v1.7 into HTML5 but I haven't taken a deep look at it (so far I've seen the <!DOCTYPE html> tag but not much more).