3 ms·

Been working with PHP since the late '90s, still do with some legacy Zend Framework clients. Lot's of people people who hate on PHP's "design" (not the code ba

Been working with PHP since the late '90s, still do with some legacy Zend Framework clients. Lot's of people people who hate on PHP's "design" (not the code bases created from it), didn't understand what was going on. PHP allows taking any C program and writing a wrapper around it, and they would often just use the C program's API, which would then become part of the PHP API for that extension . There was amazing inconsistency there, yes, when looking through a formal lens. But it was not "designed" so much as "grown" - it was an organic thing made for delivering. It was quickly able to have huge amounts of functionality added that didn't happen as fast with ASP or Cold Fusion, and I didn't find it nearly as gnarly as Perl.

tracker1 3y ago
I understood that a lot of API inconsistencies come from the underlying C libraries. For me, the biggest annoyance was in that the language itself was inconsistent with itself (not talking about libraries), array usage in particular was iirc really weird in terms of the usage functions. From what I understand it's better today and Laravel and other options can make it nice to work with. I was rather partial to Classic ASP with JScript myself... Although the biggest issue in that whole space was a lot of the addons were commercial and expensive COM libraries. VB6 added a lot of value and made it more useful. It was a much different time in the mid-late 90's though. These days, I'm still more inclined to fave JS environments such as Deno or node, that have vast and rich options for everything. Though the language itself still has a lot of detractors, even for TS. I've also been enjoying the bit I've played with Rust.