via http://twitter.com/programmingjoy/status/5857692995

I decided to re-engineer it from the ground up. JPolite V2 is then a complete re-design from the ground up with nothing from V1 except for the look & feel. The code structure is much clearer which makes it easier for customization, as well as integration with other jQuery plugins.

A new feature that is now being tested with JPolite is called XDO (XML Data Object), which currently supports JSON objects only. The whole idea is based on some discussion around “Thin Server Architecture” and REST architecture style, that a browser client first construct the foundation of a web app with STATIC content (HTML, CSS and JavaScript) from a web server, and then exchange only DATA (XML, JSON, TXT) with the application server, which relieves the server from the burden of generating HTML markup. This feature is still experimental with lots enhancements expected.

• Why REST Failed - "ERH complaining (rightfully) that browsers (and web presentation specs) should support PUT and DELETE out-of-the-box. I couldn't agree more. And yes, the title is unnecessarily inflammatory." | http://cafe.elharo.com/web/why-rest-failed/
• Carrot Vs Orange discusses the benefits, drawbacks, and arguments for or against Pie Api approaches "HTTP using GET/POST to a single URI" (Carrot) vs. "HTTP using the REST Architectural Style" (Orange or simply REST). http://intertwingly.net/wiki/pie/CarrotVsOrangeDiscuss

• via Oak Ridge National Laboratory
• How could Jeff Hawkins Hierarchical Temporal Memory be used to make sense of this data? http://www.numenta.com/

JSON ... it's the intersection of all modern programming languages. All languages have some sense of data, and structures of data. They all have simple values like number strings, and booleans. They all have some sense of a sequence of values. ... Every language has some sense of a collection of named values; it might be an object, or a record, or a struct, or a hash, or a property list, or something. All languages have these, these are universal ideas.

... But they all have the same idea about what the data looks like, and JSON has the thing that's common to everything. By being at the intersection, it turns out to be the thing that everybody can agree on, so it's really easy to pass data back and forth.

Prior data interchange formats tended to try to be the union of all the languages, and that turns out to be horrendously complex, and very difficult to deal with. JSON, by being so simple, actually became really easy to use.

Are there yet ZigBee products on the market?

Yes, there are. Some implement an actual ZigBee stack while others feature a ZigBee ready platform like EmberNet.

Examples in the residential space include Control4 (lighting), Eaton (home automation), Golden Power Manufacturing (sprinklers and thermostats), Hawking Technology (home gateways), Kalirel (heating), Mija (fire extinguishers), Nice (shutters), and TSC Systems (home automation).

Examples in the commercial space include Mija (fire extinguishers), Philips (lighting), Siemens (building automation), and TAC (building automation).

$('<ul><li><span class="library" /></li></ul>')
    .items([
        {library:'Prototype'},
        {library:'jQuery'},
        {library:'Dojo'},
        {library:'MooTools'}
    ])
    .chain();

Chain.js isn’t just bind data automatically to your HTML, but it also maintains and manages your data/items.

var data = {first:'Stephen', last:'Hawking'};
 
// Add one item
$('#persons').items('add', data);
 
// Remove item
$('#persons').items('remove', data);

via http://www.trilancer.com/jpolite2/

There are actually 3 protocols and 2 APIs that are used in Wave:

• Federation (XMPP)
• The robot protocol (JSONRPC)
• The gadget API (OpenSocial)
• The wave embed API (Javascript)
• The client-server protocol (As defined by GWT)

The last one in that list is really nothing that needs to be, or will probably ever be documented, it is generated by GWT and when you build your own Wave client you will need to define how it talks to your Wave server. The rest of the protocols and APIs are based on existing technologies.

(I wrote this article to help myself understand exactly what McCarthy discovered. You don't need to know this stuff to program in Lisp, but it should be helpful to anyone who wants to understand the essence of Lisp-- both in the sense of its origins and its semantic core. The fact that it has such a core is one of Lisp's distinguishing features, and the reason why, unlike other languages, Lisp has dialects.)

In 1960, John McCarthy published a remarkable paper in which he did for programming something like what Euclid did for geometry. He showed how, given a handful of simple operators and a notation for functions, you can build a whole programming language. He called this language Lisp, for "List Processing," because one of his key ideas was to use a simple data structure called a list for both code and data.

• Designing With Web Standards: the infamous book by Jeffrey Zeldman
• W3C Validation Engines: XHTML Validator, CSS Validator
• W3C Tips for writing clean markup, among other things.
• Introduction to Web Accessibility
• Web Standards Project - information on web standards, upcoming trends and more resources.

"In REST, “post” is used for any action which results in a resource change or side-effect, and cannot be repeated without the change or side-effect happening again. An SQL “insert” operation would be implemented as a REST “post”, for example, but so would an SQL “update” which increments a value, or the sending of an email. A practical rule of thumb is that a “post” should be simple and quick, leaving the way for future changes using “put” as soon as possible. A CRUD “create” is a quite different thing. “Create” explicitly creates a new resource, and is undefined if that resource already exists."