Specifically, the following four features are very important to me:
UI Bindings - I’m not just talking about templates, I’m talking about a declarative approach to automatically updating the view layer when the underlying model changes. Once you have used a framework (such as Flex) that supports UI bindings, you can never go back.
Composed Views - Like all software developers, I enjoy creating modular reusable code. For this reason, when programming UI, I would like to be able to compose views (preferably at the template layer). This should also entail the potential for a rich view component hierarchy. An example of this would be a reusable pagination widget.
Web Presentation Layer - We are programming for the web here people, the last thing I want are native-style widgets. There is also no reason for a web framework to create it’s own layout manager. HTML and CSS are already the richest way to do style and layout in existence, and should be used as such. The framework should be centered around this concept.
Plays Nicely With Others - Let’s face it, jQuery is pretty amazing. I don’t want a framework which comes bundled with a sub-par jQuery clone, I want a framework which recommends using jQuery itself.
Pablo Lalloni on 01 Aug 13"Protostuff is the stuff that leverages google's protobuf. A serialization library with built-in support for forward-backward compatibility (schema evolution) and validation. available formats: protostuff (native) graph (protostuff with support for cyclic references. See SerializingObjectGraphs) protobuf json smile (binary json useable from the protostuff-json module) xml yaml (ser only) kvp (binary uwsgi header) support for messages that are generated by the protostuff-compiler (java_bean) cyclic references via graph format see CompilerOptions for more customized compilation of .proto files support for existing pojos (See runtime schemas) cyclic references via graph format polymorphic (a nested message can be an interface/abstract class or even java.lang.Object) support for existing protoc-generated java messages see the io instructions for json, xml, yaml) no support for cyclic references (limitation of the builder pattern) Interoperability across various mobile platforms android kindle j2me (protostuff-me module) Transcoding support converts one encoding to another. See PipeUsage. Source and Sink protostuff, protobuf, json, json-numeric, smile, smile-numeric, xml Sink only yaml "
