If you look at this blog archive, you should see that I got interested in the MVC issue a couple of months ago. Generally speaking, I discovered that both me, and most of PHP programmers have actually never seen this architectural pattern, because web framework developers tend to call MVC something completely different. Yes, it originates from MVC, but the key concepts are different, and what is more – these derivatives do have their own names. I started wondering then, how a true MVC web application would look like, and what their pros and cons in the web environment are. Of course, I needed a playground to test these concepts and I came into an idea to create a sort of experimental framework that could help me to find the answer. This is how Trinity was born in late May 2010.
MVC is one of the most popular design patterns in the web applications. Actually, every self-respecting framework must implement it in order not to get derided by the programmers. I have been using it for a couple of years so far, but I still had an impression that something is going definitely wrong with it, until I realized that the problem does not lie in MVC itself, but the implementations which in fact do not implement MVC, but different derivatives.