Introducing JS.js

Do you ever wish that you could write awesome client side code while using a familiar syntax? Do you want to leverage powerful concepts like closures and prototypical inheritance? How about using 3rd party libraries without conflicts?

Well, your dreams are about to come true. I’m pleased to announce a brand new JavaScript library called JS.js. This revolutionary new library allows you to do so much I don’t even know where to start. I really mean it, I’m having difficulty coming up with the right combination of words to describe it. Hmm, this is awkward…

Ok, I got it. How about a bullet list of what JS.js is all about:

JS.js is unobtrusive, small (less than 500 bites uncompressed), yet highly functional.

JS.js works with all modern (and not so modern) browsers. I’m talking all current and future versions of IE (including that weird new Metro IE), Firefox, Mobile Firefox, Safari, Mobile Safari, Chrome, Mobile Chrome, Konqueror, Mobile Konqueror (I’m assuming there is one, but I may be wrong on that), Netscape, and many more.

JS.js is fully compatible with all existing libraries including jQuery, backbone.js, underscore.js, Ext js, and many others.

Intrigued? Of course you are. Excited? How could you not be. Can’t wait to get your hands on it? Wait no more, here’s the download button:

How did you like that button by the way? Impressive, no? I thought so.

Ho Do I Use JS.js?

You may be wondering exactly what your code will look like with JS.js awesoming it up. Well, here’s a code snippet which utilizes the library:

var isJSdotjsUseful = checkUsefulnessOf("JS.js"); function checkUsefulnessOf(library) { if (library === "JS.js") { return "Awesomely useful"; } else { return "Sorry, the jury is still out on " + library; } }

Did you notice it? No? Look harder… See it now? Still nothing? Keep looking, it’s definitely there. Trust me.

Why Did You Develop JS.js?

This is a great question, one with many answers, some of which probably depend on your definition of the word “why”.

I first came up with the idea for JS.js while perusing the plethora of currently available JavaScript libraries. A thought popped into my head: “It seems like every jackass with a keyboard is writing a JavaScript library these days… Hey, I have a keyboard too!“. And with that, a dream was born.

You know, it feels like I’ve been working on JS.js for years (though technically it’s probably closer to minutes). Yet, in a lot of ways it feels unfinished. It’s as if there is so much more it can and should (and shouldn’t) do.

How Can I Contribute?

Well, the best contribution would probably be a direct financial cash transfer to me, preferably in unmarked bills of large denominations. Aside from that, please feel free to spread the word about this wonderful new library as far as your ISP will take you. The web development community will almost certainly thank you* for opening their eyes to JS.js.

* Disclaimer: odds of anyone thanking you for JS.js are roughly 2,400,000:1.

You may also like:

Did you love / hate / were unmoved by this post?

Then show your support / disgust / indifference by following me on Twitter!