3 ms·
I used SmartClient when it was launched in 2002 and that did client-side rendering back then: https://en.wikipedia.org/wiki/SmartClient https://en.wikipedia.org
by jarym 7y ago
I used SmartClient when it was launched in 2002 and that did client-side rendering back then: https://en.wikipedia.org/wiki/SmartClient https://en.wikipedia.org/wiki/SmartClient - I've recently taken the JS version (not GWT) and ported it to a set of ES6 classes and modules.
I used to work for a portal vendor called Plumtree in 2004 (later acquired by BEA and then Oracle) and much of their stuff did client-side rendering.
The idea of making web interfaces more declarative and less tied to DOM manipulation has been evolving since then. Many developers I'd encounter back in those days moaned that we were not using jQuery or MooTools or whatever.
React is very nice - don't get me wrong - but its popularity has much to do with the mindset of developers shifting away from seeing JavaScript as a way of 'adding spruce' to 'web pages'.
- koonsolo 7y agoThe revolutionary part of React is not client side rendering, it's the composition (and reaction) of GUI through state changes. A quick look at SmartClient shows that it still uses the old OO way of widget composition (widgets having .show() and .hide() methods, etc). This is not at all how React works. In react you render your GUI based on state, and events never manipulate widgets, they manipulate state. It's a functional way of approaching GUI's instead of an Object Oriented way. The React way of building GUI's is now used outside of the web, for mobile apps through React Native and Flutter. This is completely different that any pre-existing GUI frameworks.
- jarym 6y agoIt does have show and hide methods - but inside the framework it is deeply compositional. If you have a chance to look at the docs search for ‘autoChild’ which achieves much the same as react and co but using different terminology.