stlab hosts modern, modular C++ algorithms and data structures.

Hacker News is a community-driven platform for sharing and discussing technology news, startups, and programming-related topics. Through user submissions and comments, Hacker News offers insights into emerging technology trends, industry developments, and entrepreneurial ventures. Readers can participate in discussions, share their insights, and stay informed about the latest advancements in technology and innovation.

Hacker News

The Model-View-Controller (MVC) pattern has been misunderstood and misimplemented over the years. The original Smalltalk MVC design keeps models completely unaware of views and controllers, using observer patterns for communication. Modern implementations, particularly Apple's Cocoa version, have corrupted this by making controllers act as intermediaries and creating tightly coupled view-controllers. True MVC requires observable models that can notify multiple views of changes, with the key insight being that models should never depend on their UI components. The pattern works as a composite where views can have their own models, and even function arguments should be treated as observable models to properly enable/disable UI elements.

How did MVC get so F’ed up?

You can thank PHP but also Ruby on Rails for that.

I never thought about MVC like that. I always do: Model = Database | Persistence; View = Client | Frontend; Controller = Server | Backend;
But it’s true. The definitions given about MVC imply that you can bypass the controller.

Massive View Controller
Magic Vanishes Continually
Makes Veterans Cry
Mostly Very Confusing
Maintainability Vanishes Completely
Mystery Vegetables &amp; Carbonara (what your spaghetti code looks like)
My Vague Conception
Mutates Violently Constantly
Model? View? Chaos!