Blog
Mert Özen's blog posts on software development, backend, frontend, and DevOps.
Why UI Architecture Patterns Exist: Separated Presentation and a Short History from MVC to Signals
UI architecture patterns exist to solve one problem: when screen code and domain logic are tangled, neither can be changed or tested. In this post we move the Bookstore order form from a Smart UI with all logic in event handlers to Separated Presentation, separate view state from domain state, and walk the history from MVC to signals together with the problem each pattern solved.
The MVC Pattern: Original Smalltalk MVC and Web MVC Are Not the Same
In the original Smalltalk-80 MVC, views observe the model and the controller only interprets user input; in Web MVC the view never observes the model, the controller runs once per HTTP request and the view renders once. We build the same order form first in TypeScript with an observable model, then with ASP.NET Core MVC, and compare the two flows along with the fat controller and anemic view model traps.