3 ms·
I did some research into MVC a few months ago for a book [1] and my understanding is that this is how it worked when the concept was first devised in those firs
by colinramsay 11y ago
I did some research into MVC a few months ago for a book [1] and my understanding is that this is how it worked when the concept was first devised in those first few Smalltalk releases: something like a textbox would still have the M and the V and the C. React just feels like a simplified version of that to me.
https://www.packtpub.com/web-development/ext-js-application-development-blueprints https://www.packtpub.com/web-development/ext-js-application-...
- derefr 11y agoSeaside (http://www.seaside.st/ http://www.seaside.st/), the Smalltalk web-application framework, does exactly what you're talking about—each component on the page has its own server-side view-controller, much like if you were using a controls library in a native GUI app. One should also note that Seaside is likely the direct inspiration for Arc's (i.e. HN's) use of links that reference stored server-side closures by ID.
- muraiki 11y agoThe free Seaside book and also the free Pharo by Example book are great ways to learn MVC. The only downside is that after using Seaside and a Smalltalk environment, you will probably be dissatisfied with not having such awesome features available in modern tools. :) Edit: It looks like there is a new Pharo book that covers more advanced topics! http://deepintopharo.com/ http://deepintopharo.com/