Programming

It's written using Symphony framework and seems to be using the latest best practice. Nothing to worry about here. PHP has its warts, which are being addressed since PHP 7.x. Modern frameworks like Symphony go even further by encouraging best practices when developing PHP WebApps, unlike the dark old days of PHP WebApps full of SQL injections and XSS issues (still is though in the WordPress plugins ecosystem).

I'm mostly a Python guy and used to look down on PHP, but changed my tune since the release of PHP 7.x. If Python has JIT half as good as PHP these days, I would die happy.

I see a lot of people quick to hate on PHP while not really knowing anything about it's modern usage... but the thing I think of most is how people praise Lemmy for using Rust and diss Kbin for using PHP, but at the end of the day it's HOW those tools are used that determines the quality of something. Language changes, but fundamentals stay the same, and in the end all anyone should care about is whether or not something works.

Programming language wars have always seemed a tad shallow to me.

Modern PHP is much better than most people expect. It has very little to do with the PHP4 we all grew up to dislike for its quirks and inconsistencies.

That said, I wish more software was done in PHP. And for me it makes a lot of sense regarding the Fediverse. A PHP platform I can put on my existing shared hosting and connect some (sub)domain to it and call it a day. Most smaller/meduim businesses probably have that hosting constellation already around, idling around most of the time. The entry barrier is just so much slower than spinning up a VPS or renting cloud space somewhere just to test a small instance of something. Sure it scales not as good as your average cloudplatform but for most usecases that is not the biggest concern.

Different product but I love Matomo as a Google Analytics because I can just copy the files to a clients shared hosting, connect a subdomain to it and if it uses Sqlite (also better than it's fame!), I am done already and don't need to create a database even.

It's not because of word press. Wordpress is complete garbage that should have died ages ago. The reason it hasn't is because it still makes it easy for people to add a customizable site in a couple of minutes.

As for php, the php 5 days are long gone. Php has actually become a good a respectable language since the release of php 7, and things only continue to improve. Php is at version 8.1 and progress is not slowing down. There is even a dedicated full time dev team for php now. PHP is definitely not going anywhere any time soon and I'm more than comfortable with starting new projects using PHP. It happens all the time, especially with support from extremely good and well established frameworks like Laravel.

Honestly if you're starting a new project today, what would be a joke is to start it in node.

Mature web framework and highly productive language vs less mature framework and emerging language. Personally, I think Rust is the more surprising pick than PHP for this application. A link aggregator is a forum with some frills. Not to mention half of the activitypub implementations that I know of have been in PHP.

Does disappointment count?

After struggling my way through a broken MediaWiki upgrade today, I was reminded once again of just how awful PHP is, both to develop in it and to use applications written in it. What I had to deal with today would not have happened if it were written in a compiled language, because it isn't possible in compiled languages.

Specifically, my MediaWiki settings file contained:

require_once( "$IP/includes/DefaultSettings.php" );

Apparently, this was once required in MediaWiki settings files. After upgrading, though, its presence causes an extremely misleading error message:

Fatal error: Uncaught FatalError: $wgBaseDirectory must not be modified in settings files! Use the MW_INSTALL_PATH environment variable to override the installation root directory. in /path/to/mediawiki/includes/Setup.php:237

My settings file does not contain $wgBaseDirectory. Moreover, adding $wgBaseDirectory = MW_INSTALL_PATH; to my settings file does nothing.

Only after a lot of web searching (and a fair amount of profanity) did I finally find out that the above require_once statement is the culprit.

See the problem here? Interpreted languages like PHP encourage the extremely irritating anti-pattern of using an executable code snippet as a configuration file, which inevitably results in this kind of nonsense. In a compiled language, on the other hand, the easiest way for an application to load settings is by reading them from a data-only format like JSON or TOML, parsers for such formats tend to produce better error messages than this, and the vast majority of such formats don't have an include directive at all.

Had MediaWiki been written in a compiled language instead of PHP, my morning would have been a whole lot less stressful. And this isn't the first time that this configuration-is-code anti-pattern has caused me grief.

I'm a web developer of 25+ years. These days python, php, react, vue stack. Formerly, C, C++, perl and assorted other oddities.

Forget what you once heard about PHP. Modern php is nothing like its early days. Modern php has some great constructs that give language expressiveness and fluidity, and that really lends itself to concise and beautiful code.
PHP also has some brilliant web frameworks (eg: Symfony) that make build web apps (be it REST APIs or frontend backends) just a pleasant experience all around. It's dead simple yet extremely powerful. This makes makes development and maintenance using PHP cheap. PHP's testing suite is also ridiculously powerful.

By comparison, I find python web frameworks (Django, flask etc), fiddly and finnicky to use. I also find Python a much less expressive language. By that I mean it will often take me several lines of code to do something that is otherwise a 1 liner in php. It just feels clunky and awkward.

Don't get me wrong. I once hated and laughed at PHP with the rest of them. But PHP has really evolved over the past 10 years, much more so than python has. I look forward to the day Python has a good hard look at itself.

In the meantime, if I need a backend for a website and I'm given the choice between PHP or Python, I'll choose PHP (symfony) every time.

Besides, PHP devs are cheaper.

First off, any language/framework is just a tool.

Second, modern PHP is quite different than 2005 PHP which is about when people started moving to other languages for web development (Ruby, Python, etc.). What you can and should write in PHP today would be almost identical to what it would look like in those languages (i.e. MVC frameworks, ORM for DB access, dependency management with lock files). Many language features were added too such as namespacing which allow for better/modern code organization.

PHP has always had (and never lost) it's dead simple capability to just package up a tar ball, ftp, unzip and just... run.

Would I use PHP today, not unless forced to or for a lot of money. But if it's a language a team knows, there isn't a benefit to switching to something else.

Not too surprised. I know PHP has a reputation these days of being old and crufty but at the same time there hasn't really been a killer replacement yet for the same use cases where PHP is/was used. React and Vue are all the rage for frontend work, but their paradigm is all about single page apps which is a bit limiting for something on the scale of Kbin. Other backend frameworks like Django tend to be fairly opinionated and lock you into developing in a certain way without providing a large enough benefit to make it worth it.

IDK maybe there are better frameworks that I just haven't heard of. But whenever I go to start personal projects, the options seem to be Express, Flask, or PHP, all of which have their own tradeoffs. Personally I lean more towards Express or Flask but it's not surprising to see people stick with PHP.

In my opinion, only the most elite (in all the wrong ways) people care how you build your app.

PHP has flaws, sure[1]. But unless you are working on the app itself (or again, you are horribly elitist) it does not matter.

What matters is that the app is good. If the app is good, it doesn't matter that its done in PHP, what matters is that it works.

EDIT: I guess it also matters if you're selfhosting the app.

[1] I think PHP is overhated. As a stateless language it lacks a lot of complex features (and thus, admittedly, might be questionable for a project as large and complex as kbin), it has some questionable design decisions, but it's really not as bad as people make it out to be.

Same reaction. Rust is the future. Typescript is the present.

PHP is not as shitty as it used to be. Additionally, it's very approachable and it runs basicly everywhere.

Funny that a lot of people responded by bashing on PHP, but I saw very little real arguments why PHP is so awful. What makes PHP that bad besides being the target of memes?
I mean "lame", "old" or "dead" aren't particularly convincing arguments.

I don't know too much about PHP (aside from it getting memed on constantly), but kbin is built using the Symfony framework, which is really performant and mature based on what I've heard from others. Also, apparently ~80% of all websites (that W3techs knows about) rely on PHP in some way

Large parts of my particular departments .gov.uk stack are PHP. All modern (8.1+) using established frameworks and to be honest, it's a joy. It's quick to write, easy to understand and very easy to test. The write, run, debug cycle is also essentially instant; although I really enjoy using Go (another bit of the stack) being able to quickly iterate changes is something I absolutely miss when I'm using it.

Laravel + Livewire is some sort of dark voodoo magic. I can write only PHP and have a functioning SPA with push updates and all sorts.

There's still lots of active PHP projects, including new ones. PHP is actually a nice language and much of its negative reputation comes from the years of stagnation during the late PHP 5.x era. Which is long over. I definitely find PHP to be much nicer than JS for backend development, although I no longer use it professionally.

It's such an outdated meme to shit on PHP. PHP 8.3 is absolutely nothing like PHP < 5. It's become a full-fledged, performant and secure language. I've been coding PHP since 2005, and I've seen it grow and become incredibly capable. Sure I do recognise that other languages are still more "popular" and respected, and as such I've been focusing more and more on Node/Typescript in recent years, but PHP isn't going anywhere. And its package ecosystem is so much more reliable and stable than say NPM.

I know it sounds childish but PHP is lame as hell same as java. Rust or go would have definitely been a cooler choice. I mean PHP gets the job done, but still....

more so surprised that it wasn't written in {insert favourite language here}

that being said I agree that PHP isn't anything like it used to be.