Amplify: a jQuery component library for solving common web problems.

Wow, this is exactly the kind of interface I dislike. It's way too verbose and I'm not sure why one would add this kind of layer on top of jQuery. I don't see where it makes things easier - it's more like it just provides yet another interface.

<i>Amplify is a set of components designed to solve common web application problems with a simplistic API.</i><p>Pretty sure the author means 'simple' rather than 'simplistic.' It's an important distinction!

This is not my cup of tea.<p>1. I don't like magic string names like "AjaxExample1". Why not return an object, and use:<p>var AjaxExpample1 = amplify.request...<p>2. It is not clear how you mix get parameters and post data. If I want to POST to "/users/{id}/", how do I separate the post values from the parameter?

Three mediocre plugins bundled into one? Sorry but this left me underwhelmed.<p>There are much more powerful plugins for each of these problem spaces.

Would love to see someone explain what this library does in simpler terms. I can't tell which terms are buzzwords, which are industry standard, and which terms are from their own internal vocabulary. PubSub? PubSub to what? Can you give some real world examples of when to use this library and what problems it solves.

There's a typo in the first example. You're missing a '1' in the first argument when you execute the ajax call.<p>The pub/sub is all local right? I got really excited, then not so much. I still see the value, but I was hoping it was more like Google's javascript+serverside-component PuSH client. [1]<p><a href="http://code.google.com/apis/feed/v1/devguide.html#hiworld" rel="nofollow">http://code.google.com/apis/feed/v1/devguide.html#hiworld</a><p>(It's really cool, Google runs a PuSH bridge so their server side component subscribes to a Pubsubhubbub hub and receives updates and pushes them to the browser. I want to see an OSS implementation of it since it's really slick and PuSH is a neat protocol).