A petty rant but I'm going for it anyway.

I don't like how Trongate is bashing Laravel, claiming that it is a "better" framework and "Pure PHP is back".

It's fine if you built a framework that is better than Laravel, good for you. But don't go around bashing Taylor Otwell's work. As someone, who has spent a major portion of my career in IT as a Laravel dev, that hurts to see.

IMO I think they never understood why Laravel became popular in the first place. It wasn't because it's the fastest, but because how beginner-friendly it is and how easy it is to maintain and many other perks it has.

I checked the website, they advertise it as way faster than other frameworks but checking specs and code, it seems to me like an other cms based engine instead of a framework.
Feels limited compared to laravel at first glance. But I can't say for sure till i try it.

Modules market? This is just trying to be another wordpress.

Also, they claim to be pure PHP but their source code is really devoid of many modern php features.

I don't see return types anywhere.

When SQL queries are present in the code, they do not use indented heredoc.

And I haven't seen use statements.

I think by "pure PHP" they mean 0 dependencies functional approach. But with classes and modules that have to be loaded with functions...? It's reinventing the wheel.

Their source code isn't very pleasing to the eye. Reminds me of the kind of PHP you see in "Why I hate PHP" examples

Definitely getting Wordpress vibes.

Fucking <style> tag in the middle of the Model class.

Their documentation uses Comic Sans for the "Important" bits. I'm starting to think you've bamboozled me.

Also, "This framework is not available on composer or packagist."

@nitnip Holy shit lmao

@nitnip wow that dependency injection is something else. Reminds me of a legacy project I worked on that was developed before composer was widely used.

Link to Trongate bashing laravel pls?
@nitnip I skimmed through the docs, I like its idea and there's not rly something inherently wrong with not using optional new language features, but it does look like it's in need of some polish and definitely not in the place to "bash Laravel". It's logical you will gain speed by not using advanced constructs or optional psr libs and using define's and globals. But will your code be as robust?

Also, someone else got scammy vibes from the homepage?

@webketje I suppose it's somewhere in here: https://trongate.io/framework_wars

I just feel like the code is hard to read, there is no helpful comments and of course it is going to be marginally faster by

a) not using a templating engine

b) not implementing a middleware stack to go through on each request

c) inlining html and styles

It's just going to be a lot harder to maintain. Also, the people using this will need external libraries most likely, so that means bringing in composer and having to do extra work because the psr4 autoloading won't work right from the start.

As far as "faster" PHP framework concepts, I much prefer Ubiquity (it even looks nice) and PhalconPHP (built in .so extension).