Essays

There is sometimes a tendency within the PHP world to treat Composer, Packagist and PSR-4 as though they are inseparable parts of modern PHP development. They are not. They are three separate technologies and concepts that often work together, but they do different jobs. More importantly, there is no requirement for a PHP framework to build its core architecture around them.

Recently, I came across a product being discussed online called "NativePHP". The name immediately caught my attention, not because of controversy, but because of similarity. Within the Trongate space, the phrase "Native PHP" has been used for some time. Same words. Different spacing. Very different meaning.

When Trongate v1 was released, I made a bold promise: v1 forever. That promise reflected a commitment to stability in an industry obsessed with constant change.

If you're expecting Trongate v2 to dazzle you with a long list of shiny new features, lower your expectations. This is not a story about adding more. It is a story about removing what was never essential in the first place - and why doing so matters more today than ever before.

Let us address the elephant in the room. When developers hear the phrase lightweight framework, many instinctively translate it as toy project or learning tool. This reflexive assumption has cost the industry countless hours of unnecessary complexity and significant operational overhead.