Angry Coding

In old times, when JavaScript libraries had to work only in the web - browsers, common pattern for exporting your stuff into the global namespace was looking like this:

(function() {
    window['MyLibraryMethod'] = function() {
        alert('HELLO WORLD!');
    };
})();

We were just attaching our methods and properties to the global namespace, and this was all fine before somebody come up with the idea to run JavaScript code in non - browser environment. There was no window object so we had to find global object ourselves:

(function(global) {
    global['MyLibraryMethod'] = function() {
        alert('HELLO WORLD!');
    };
})(function() { return this; }.call(null));

Then things started to change very quickly, CommonJS standard and it's implementations against AMD (Asynchronous Module Definition), RequireJS and so on, but how should I package my library so the end - users won't have to repackage it in order to use it?

Nowadays HTML5 becomes more and more popular, offline cache can help you when you need to build an application that does not require a web - server, client - side storage can be used to store application data in built - in web - browser database. But what if you need to share application data between users? There are many web - applications that allows you to share your work with the rest of the world, for example jsFiddle allows you to save your code snippet and get a permanent link that you can post in twitter or send to your friend. So how can you make something like this using HTML and JavaScript only?

Histone template engine now has it's own online playground application that allows you to test your templates and play with examples right in your web - browser.