We used to write thick clients, fat happy Swing apps that executed application logic and business logic on the user’s computer, and connected to the server mostly for data access. Then we moved toward service-oriented architecture and the thin, browser-based client. This solved all our deployment problems, and it moved the business logic back to the server.
Think about apps that run in a browser, but aren’t dependent on constant network access.
What’s the negative? 3 megabytes. yikes! and it’s not out yet, so you can’t play with it.
But hey, the
thick rich client is back, still functional when the server is unavailable, and it is integrated into the IDE (Smalltalk lives!). Just think, no session data on the server — that smells like freedom. We’re bringing the code to the data again, where this time the data is user input. This bodes well for responsiveness.