Google’s Polymer and the future of web UI frameworks
2ality.com
2ality.com
The best I can relate it, is that I can take all the widgets that are used throughout the website and wrap them up into their own CSS and JS. No need for rigorous CSS namespacing, JS modules, etc. It's all packaged up, ready to drop into an HTML page. The most interesting part are the polyfills for the various Web Components, erm components, that are currently being drafted. At the moment, the polyfills have to implement most everything but eventually won't be needed when the specs are finalised and the browsers caught up.
Also, maybe you have a weird definition for "widget", but go watch Bret's latest talk. It's all widgets. And it's certainly not dynamic magic; we can build interfaces like that, but more and better tools to make building them easier are a very good thing.
I'm personally really excited from what I've seen of Polymer, and even more excited about its mostly decoupled design (and the polyfill-until-standardized approach the GP comment mentions), allowing you to pick and choose what you want to use without committing to some huge (and "opinionated") framework.
Opinionated frameworks are great, until you need to do something they didn't anticipate. If you're lucky it's easy to work around, and if you're not then welcome to your latest nightmare.
The whole polyfill concept is exactly what the world needs to allow browsers to grow and mature at different rates.
No, it's not. I'm sure you had something else in mind by that.
More on this is going with web-components: https://groups.google.com/forum/?fromgroups=#!topic/polymer-...
Seaside makes it extremely easy to embed multiple components within or alongside each other. It also has the ability to sequence the display of components in a modal fashion while synchronizing the client state (even when using the back button), which can be good for some types of wizard-style workflows.
In terms of using Smalltalk, the message-passing syntax is elegant and simple to comprehend. And the ability of Smalltalk to aid in debugging is fantastic: if you running web app experiences an error, you will get a debugger with a stack trace that includes the source code of everything in the stack. Simply make the changes necessary to fix the bug, and then resume the execution of your program. If you like REPL style coding, this is quite similar, albeit through a GUI. This has proven invaluable to iterative development.
There are two great free resources to learning Seaside. The first is Dynamic Web Development with Seaside: http://book.seaside.st/book Another good one is An Introduction to Seaside: http://www.hpi.uni-potsdam.de/hirschfeld/seaside/tutorial
Less related to polymer, I feel like a lot of proposed standards get implemented in Blink/Moz when one could accomplish the same thing with a polyfill to see if it's a good design or not. ShadowDOM is an example of this as it exposes a huge new interface surface area. Mutation Observers are a good counter-example since it's a small API and is well defined.
To me it seems like there is a little bit of convergence.
I know this is going to be controversial but -- I actually believe that eventually web, mobile and desktop platforms will be the same thing. Because they actually share so many goals, use-cases, and especially, technical challenges.
For example, new UI frameworks and application builders coming out, at least for the web, are definitely trying to provide a one-stop shop for web _and_ mobile devices. Or another example: Google Now voice search functionality appearing in Google desktop.
One reason for this is because a large portion of the problems that developers need to solve are actually the same on each device. I will even go so far as to say that desktop machines will start to become identified and have persistent payment systems the same way that mobile devices do. Because most desktop devices actually are used by only one person and there is a huge convenience win there.
You can already see people moving away from desktops and towards laptops. Or people using their mobile phone almost as if it were a laptop with a tiny screen and slow keyboard. You see people working on the go from coffee shops more and more.
With more and more capabilities coming to browser applications, pretty soon people will start to realize that the only important thing that their browser can't do is break out of the confines of the browser tab and create notifications. Browsers already have convenient APIs for key devices.
So I believe that the remaining limitations of browser applications will go away, and we will see a component-based web application framework that doesn't even show an actual web browser.
But really, being able to take a laptop with me is nice, but I would rather not have to carry anything. That's why I think that Google Glass is a look into the future of computing. But I think within 10 or 15 years we will go even further than Glass. We will end up with one web/desktop/mobile/brain platform that interfaces directly with our brains.
I think I am rambling again sorry :)