Just looked at Laravel, and it feels like its trying its hardest to lipstick the PHP warts. When i look at a framework like it i see just bloat. You really only need like 5-10% of stuff thats there. Thats why its most likely slow and heavy, and looks like it was cowboy copied from some legacy .NET enterprisey framework from the early 2010s.

Jobs? Sure. There are PHP jobs, and the PHP devs are a dime a dozen. But i will agree with you, Laravel is a fine pick for websites, but not so much for more real world, high load applications.

Theres also 100x more jobs for WordPress than Laravel, so if you want to do PHP, i suggest going the WordPress route instead.

That’s a strange thing to say. If I wasn’t self employed, I’d pick the job that pays more (Laravel) instead of the job that (according to you) is 100x more available.

And who really cares about bloat anyway? Hardware is super cheap nowadays. People are expensive. So why not use a framework that enables you to be (in your terms) 100x more productive?

On top of that, you’re arguing about languages and frameworks you’re not even familiar with. Why does your opinion matter at all?

> And who really cares about bloat anyway? Hardware is super cheap nowadays.

That told me all i need to know. When you work on missing critical software bloat is usually THE killer in disguise. And its really hard to get rid of after a certain point.

> So why not use a framework that enables you to be (in your terms) 100x more productive?

Because i can be just as productive, and even more so by vetting, and choosing my dependencies with some hindsight. I dont cowboy pick some hype of the day thing, i take a real close look at the code and want to actually understand whats happening.

> On top of that, you’re arguing about languages and frameworks you’re not even familiar with.

I am indeed familiar with the PHP ecosystem, been there and done that.