🇺🇦 Anna FilinaMar 30, 2024

This looks suspiciously similar to azjezz/psl, just with a different API. It even has the same name: PHP Standard Library.

The PHP community would be better if devs worked together instead of copying and re-branding someone else's work. Credit to azjezz for the original PSL.

Show threadJørn

@afilina Today I learned that there is something called "PHP Standard Library", which is something different than SPL, the Standard PHP Library that's included with PHP: https://www.php.net/manual/en/intro.spl.php

I wish people would first check what the language actually has to offer, before trying to implement functionality resembling Ruby, Java, Python, Brainfuck or whatever in PHP.

PHP: Introduction - Manual

Mar 30, 2024 at 10:48pmWeb
Show thread🇺🇦 Anna FilinaMar 31, 2024
@jornane This doesn't bother me though:
- Projects with PHP in their name, such as PHPMailer or PHPUnit, are common.
- PSL and SPL: one is a package and the other is part of PHP. Most PHP devs don't refer to SPL in conversation. It's just PHP. It could have been better named, but doesn't cause confusion.
- The PSL package doesn't re-implement existing PHP functionality. It offers new features. Perhaps I misunderstood the concern here?
Show threadJørnMar 31, 2024

@afilina Using PHP in the name would be fine; this indicates compatibility. My concern is using "Standard" in the name of a third party library. Better would have been to name it after it's async nature.

Even though PSL and SPL are different things, the name confusion is there. I'm not calling a library "composer" either, even if I'm making something very different from a package manager.