Stop-saying-PHP-is-dead

#1

Post by deepender99 » Fri, Dec 04, 2020, 8:13 PM UTC

Re: Stop-saying-PHP-is-dead

#2

Post by VincentOrback » Fri, Dec 04, 2020, 8:47 PM UTC

I mostly heard, yeah it’s not great but I’ve been doing it for so long..

But hey, I’ve been doing it for a while to, so how can I learn to write more beautiful php? And do you only use it for backend since you said “we don’t do php in html anymore”?

Re: Stop-saying-PHP-is-dead

#3

Post by mandragon » Fri, Dec 04, 2020, 9:01 PM UTC

PHP for web is great but you'll still want to use another technology for real time functionality, such as: Elixir/Phoenix, nodejs, Go, Java.

Re: Stop-saying-PHP-is-dead

#4

Post by wwweston » Fri, Dec 04, 2020, 9:06 PM UTC

mandragon wrote: post #3

PHP for web is great but you'll still want to use another technology for real time functionality, such as: Elixir/Phoenix, nodejs, Go, Java.

I really actually like PHP in a lot of contexts (and think I could make a better case for it than the author), but on the project I'm working on now, we recently got hit with the real time requirements and I'm feeling some regrets that I didn't pick Elixir+Phoenix to start with.

Re: Stop-saying-PHP-is-dead

#5

Post by mandragon » Fri, Dec 04, 2020, 9:20 PM UTC

wwweston wrote: post #4

mandragon wrote: post #3

PHP for web is great but you'll still want to use another technology for real time functionality, such as: Elixir/Phoenix, nodejs, Go, Java.

I really actually like PHP in a lot of contexts (and think I could make a better case for it than the author), but on the project I'm working on now, we recently got hit with the real time requirements and I'm feeling some regrets that I didn't pick Elixir+Phoenix to start with.

Phoenix does offer a pleasant, streamlined full stack experience, and it does seem kludgey to bake together PHP and Phoenix without good reason.

If I didn't have a team to deal with a large Elixir codebase (a common issue), I'd glue PHP and BEAM together anyway, even going as far as to pass along the "meat and potatoes" backend work to PHP even for socket interactions (or in some asynchronous way, as needed). In that scenario, the Elixir sockets frontend could be fairly minimal, both in terms of codebase and DB interactions, and would possibly not need a lot of code changes over time.

Re: Stop-saying-PHP-is-dead

#6

Post by opless » Fri, Dec 04, 2020, 9:24 PM UTC

Php has been dead for years.

Re: Stop-saying-PHP-is-dead

#7

Post by sayjava » Fri, Dec 04, 2020, 9:26 PM UTC

What’s the use case for php in 2020?

Re: Stop-saying-PHP-is-dead

#8

Post by sayjava » Fri, Dec 04, 2020, 9:27 PM UTC

What’s the use case for php in 2020 though?

Re: Stop-saying-PHP-is-dead

#9

Post by aaaaarghZombies » Fri, Dec 04, 2020, 9:29 PM UTC

VincentOrback wrote: post #2

I mostly heard, yeah it’s not great but I’ve been doing it for so long.. But hey, I’ve been doing it for a while to, so how can I learn to write more beautiful php? And do you only use it for backend since you said “we don’t do php in html anymore”?

I think you might have the wrong end of the stick.

Re: Stop-saying-PHP-is-dead

#10

Post by theSIRius » Fri, Dec 04, 2020, 9:33 PM UTC

I really can't think of any green field project that would be started with PHP today. Maybe if there is some specification to use something PHP specific. But any use case I can think of, Python or node is a better choice. Maybe even Java. And Rust is on the rise now, in case speed is needed. PHP isn't dead yet. But it definitely is not growing.

Also arguing that choosing a language based on ugliness is a stupid idea is a stupid idea on itself. Quality of life during development is not an insignificant thing. The resulting project will suffer greatly if the chosen language makes me want to tear my hair out.