this post was submitted on 16 Jun 2023
72 points (100.0% liked)

Programming

13366 readers
1 users here now

All things programming and coding related. Subcommunity of Technology.


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 1 year ago
MODERATORS
 

I don't know if it's due to over-exposure to programming memes but I certainly believed that no one was starting new PHP projects in 2023 (or 2020, or 2018, or 2012...). I was under the impression we only still discussed it at all because WordPress is still around.

Would a PHP evangelist like to disabuse me of my notions and make an argument for using PHP for projects such as Kbin in this day and age?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 1 year ago (2 children)

Massive PHP hater here!

Yeah, even outside the loop I know that, just like every other major programming language, it has grown a lot to mature with general coding practices. It's reasonable well suited for something that has tons of server side content.

[–] [email protected] 1 points 1 year ago

Kudos for saying that even as a massive PHP hater :)

IMO there is a reason why Wordpress is so popular (Disclaimer: massive Wordpress hater here!). Because of ease of install, more people can upload some folder in an (Web)FTP client than spinning up a Docker Container somewhere to host the latest JS Framework of the day just to host their little page or to show their content.

There is simply no need for bundlers, preprocessors and often not even [a lot of] package management (I'm aware of PHP composer though)

And exactly that ease of install is what could IMO make the Fediverse more democratic than having to run a container at some VPS that only a comparetively few people are able to do.

[–] [email protected] 1 points 1 year ago

I went from PHP lover to PHP hater about a decade ago. I have to admit, reading some of the Kbin code has made me hate it a little less. It's nice not to see include() and require() everywhere. It's also nice to see some type safety features as that was the biggest reason I moved on. For anything much bigger than a simple script, even if you think you won't, you're going to struggle without it.

It's still not my first preference (and, let's face it, most of this is preference) but it looks a lot better.