Let me clear up some confusion here. First, thank your for following up to this thread, it helped me to understand your position better. What your comments also taught me, is that I need to be way more precise when writing a post like this.

Firstly, I was mostly talking about languages like JavaScript that are running directly within the browser. When it comes to Back-end-techniques I don't see the necessity for this type of improvement, especially since most languages there are compiling before a request even comes in (or include some neat ways to cache the output).

To be clear: I haven't thought about using this "Snippet"-technique for software running on your mac/pc, it's thought for the web. I don't care about disc space or anything like that, in this post, I was just thinking of a new way to limit the size of the data packages that are downloaded from the server, each first time someone visits a site. And this "first hit" is really important to me and to many other developers out there. It's the first time a website or -app is actually downloading to a visitors client. Therefore I'm pretty focused on making it a good experience for the user.

I'm also thankful for that "compare 1 line of code to call library function versus e.g. 15 lines of code snippet" argument, I completely agree with you there. But when I say "snippets", I'm actually talking mainly about JS-functions (for example) that can be called on a specific DOM-Element, Object, String or whatever.

You can also take a look at the comments on my site, I posted a comment about "dynamic frameworks", maybe that will be a proper solution for the future. But as I already said, as long as this is not real yet, the "Snippet"-technique is probably the best way to achieve fast web-applications, in my opinion.

Sorry for not stating everything clear enough, again. I will make sure to do better in the future. :)