Changeset 05217bb for content

Timestamp:

Jul 16, 2022, 1:08:43 PM (2 years ago)

Author:

Mikhail Kirillov <w96k@…>

Branches:

master

Children:

4d3065b

Parents:

8ff16b8

Message:

Php add one sentence

File:

• content/en/posts/php-review.org (modified) (1 diff)

content/en/posts/php-review.org

@@ -161 +161 @@
 
 *** Why procedural OOP might be bad
-Symfony and PHP heavily rely on OOP. I don't like several things in that
-paradigm. The first is access modificators which makes a developer of a
-library in charge of its user. Luckily there is reflection in most OOP
-languages, so you can extend anything you want. Many people think it is
-bad, but library devs can do mistakes or just abandon their libraries
-and you want to modify them to work. The second is Inversion of Control
-pattern. It is bad mostly by the same reason as the first one, you lose
-control over some code. Instead of you running the code it is someone
-else running your code (mostly classes).
+Symfony and PHP heavily rely on OOP. I call it procedural because it is
+not like Smalltalk or Lisp OOP where you can extend anything. I don't
+like several things in that paradigm. The first is access modificators
+which makes a developer of a library in charge of its user. Luckily
+there is reflection in most OOP languages, so you can extend anything
+you want. Many people think it is bad, but library devs can do mistakes
+or just abandon their libraries and you want to modify them to work. The
+second is Inversion of Control pattern. It is bad mostly by the same
+reason as the first one, you lose control over some code. Instead of you
+running the code it is someone else running your code (mostly
+classes). Also as I said before because PHP has tons of C under the hood
+you can't modify standard library which is sad.
 
 This is not so critical since all the code is available for free as in