3 ms·
There was never anything really wrong with PHP, just things that - to a computer science student, who just wrote some recursive-descent parser for C++ in OCaML
by phendrenad2 3y ago
There was never anything really wrong with PHP, just things that - to a computer science student, who just wrote some recursive-descent parser for C++ in OCaML - will seem inelegant to an embarrassing degree. But that doesn't actually matter. The benefits of PHP easily overruled those inelegancies. When you look at the average Ruby/Python/NodeJS project that's been around for more than 10 years, you'll see horrors beyond human comprehension, just like PHP.
- naiv 3y agoAbsolutely true. Especially for javascript and people who do not understand typescript. I think op is having more of a problem with languages that are not fully typed than php per se.
- somewhereoutth 3y agoTyping is no protection against metastasizing complexity - indeed it adds another layer of code-like 'agar' for such complexity to inevitably grow in.
- lioeters 3y agoComplexity as a kind of mold culture, growing on the substrate of code and code-like typing, suggests the importance of sterile practice and hygiene, like testing.
- askonomm 3y agoI think my problem is not entirely in languages that are not fully typed (although I do prefer them), but rather in languages that are half typed. Either be dynamic or static, not some awkward middle point. Perhaps PHP will get there eventually, but as it is right now is a bit strange to me.
- deleted 3y ago[deleted]