[phplovesong]

I guess if the team is (only?) familiar with Perl. But then again, its the same with PHP. Even IF you know PHP you would not pick it over the more modern alternatives in 2024.

I guess some people just want to stick with what they know, and refuse to learn anything new.

[victorbjorklund]

Whats wrong with PHP with laravel for a web project? How is it worse than say python with django?

[7bit]

Nothing is wrong. Commenter is generalizing and shelling out "hot" takes

[7bit]

> Even IF you know PHP you would not pick it over the more modern alternatives in 2024.

That really depends on the use-case. If you need a batteries-included web framework, the top 3 that come to mind are Spring (Java), Django (Python) and Laravel (PHP).

And Laravel is a very good framework.

[chuckadams]

Let's not forget Symfony, the foundation that at least half of PHP frameworks including Laravel are based on.

[jprete]

I recently read a new idea of why PHP is useful to people - it's the lowest-overhead server-side Web page language available. If you want a tiny amount of functionality, you write a tiny amount of PHP and don't have to do anything else. So it scales much, much better in the tiny-to-medium-sized project range.

(I can't personally vouch for the claim but it's the best explanation I've heard for how such a reviled language has survived this long.)

[SoftTalker]

If your language is used widely enough to be reviled, you’ve been pretty successful.

[lupire]

PHP is the meth of web programming.

[monooso]

Plenty of people choose PHP for new projects, for perfectly valid reasons.

[lordgroff]

I run a WordPress site for my wife's business. Would I pick it up again in 2024? Absolutely. It has nothing to do with what I "know", there's still no better CMS/ small diy e-commerce solution for, frankly, peanuts in hosting.

I really don't have much issue with modern PHP either, it gets the job done and unlike Perl is still very much evolving.

[Sakos]

I think there are worse things than modern PHP (speaking as somebody whose primary contact with PHP is being traumatized by legacy PHP 7 projects). Afaik, the only places that will start a new PHP application today are places where the expertise is in PHP and Laravel/Symfony. I don't see a big enough benefit from migrating to a whole new stack that wouldn't be accomplished by some focused maintenance and refactoring if you're already working with PHP 8.1.

[EternalFury]

I would pick PHP for its intended use, web dev without fat clients. Laravel is the best framework I have ever used…and I have used them all.

[chuckadams]

I write PHP for a living and I only write headless apps with Symfony and Laravel. Blade is an awful template engine with a primitive parser. Twig is tolerable, but for me nothing beats the DX of Inertia with Vue.

[EternalFury]

You are most likely right. I just fear spreading complexity everywhere. But I also want to take advantage of the vast compute available at clients. So, I am conflicted. Vue is probably a good compromise. Please share your best references on Inertia/Vue.

[chuckadams]

Only deployments of Inertia I have are internal code I can't readily share, but all it does is replace the very typical pattern of passing json-encoded props to a a blade template that contains a single React/Vue/Svelte component. Now you just return Inertia::render('My/Component', $arr) from your controller or route handler function, and you're good to go.

It also has various magic for router links that do partial refreshes and working with classic (non-json) forms and whatnot. I use none of those, I'm all about json and useFetch() instead, and Inertia's pretty good about getting out of your way when you don't need it. It lets you write as much or as little in SPA style as you want, it's more or less your favorite JS framework as a view layer directly without having to interpose another view as a middleman (the middleman is there, but it's all implicit: you add the @inertia directive inside your <div id="app">, and that's it)

[slim]

you should try API Platform

[chuckadams]

I'm familiar with API Platform, it's the bees knees. Documentation could be better though.