I Said There’d Never Be a Version 2 – I Was Wrong

Over and over, I promised there would never be a version 2. Turns out, I lied.

Development on Trongate v2 is now well underway, and it will be released before the end of the year.

What’s Wrong with Trongate v1?

Trongate v1 has served us well, and there are many things that I’m genuinely proud of. However, a few mistakes were made along the way - and they were entirely my fault. One of the biggest was simply building too much. By continually adding features to the framework, it gradually became more complex and began to resemble a slightly bloated content management system. Moreover, by introducing additional tools such as the API Manager and Trongate Pages, we inadvertently drifted away from the original idea of Trongate being a simple framework built around “pure PHP”.

Another mistake I made was with the Desktop App and the Module Market. I underestimated how reluctant people would be to download and install a desktop application. As for the Module Market - it has remained in a somewhat unfinished, rather lacklustre state for quite some time. When Trongate MX appeared, I instantly recognised it as the perfect solution for building the new Module Market. Of course, that realisation had the side effect of demotivating me from working on the old one. And, as if by magic, a whole lot of nothing happened.

The final mistake I made was the biggest of all - me.

For a while, Trongate appeared to be a one-man show - and that’s not healthy for any framework. I’ve known this for some time, which is why I made the decision to gradually step back. It was the right decision. I no longer plan to - for example - post regularly on the forum, nor do I wish to keep engaging in things like “Framework Wars” or playing the part of the loud-mouthed, obnoxious guy. I’ve done that for a while - and, to be honest, the novelty has worn off.

Over the years, I’ve argued that PHP needs a framework built around simplicity and zero third-party dependencies. I’ve also insisted that the PHP community would benefit from an alternative kind of framework - one that uses what I would call “pure PHP”. For a long time, it felt as though I was shouting into the void. I’ve certainly managed to irritate a few Laravel developers along the way. Nevertheless, the time has come for me to draw a line under that. To be clear - I stand by every word I’ve said about the need for an alternative kind of PHP framework. However, I’m done banging my head against the wall and dealing with a community that seems to actively punish innovation.

So, while the other frameworks continue to grow heavier and more bloated, Trongate will quietly tick along. I, and those who stand with me, are not going anywhere. We’re just going to keep on coding.

What to Expect from v2

With v2, Trongate is returning to its roots. You can expect a framework that is even simpler, leaner, and faster.

Instead of adding more, my focus this time is on removing everything that isn’t essential. The good news is that - from an architectural standpoint - Trongate will move towards a more mainstream structure. So, instead of using the rather eccentric term “Hierarchical Assets View Controller” (a slightly ridiculous phrase I utilised to make me feel intelligent), Trongate will adopt a cleaner, more standardised “modular MVC” architecture. This will give developers coming from other frameworks or programming technologies a sense of familiarity.

As for the code itself - the top priority is ease of use. Trongate v2 is being developed from a “syntax first” perspective. This means that whenever a new feature or improvement is considered, the process always begins with one simple question:

“What would be the absolute easiest and most intuitive syntax for doing this thing?”

Once the syntax feels right, the building begins.

I honestly don’t know how Trongate v2 will be received. I’ve lost faith in metrics like GitHub stars. I have also come to terms with the thought that Trongate will probably never get mentioned at any of the big PHP conferences or by any of the self-appointed code police. Those people see Trongate as a threat and I don't blame them. It matters not. The flags are flying, and there are some truly great people behind this framework.

Our determination to make Trongate the best framework in all of web development remains as strong as ever.

DC