On Thu, Feb 8, 2024 at 4:02 PM Григорий Senior PHP / Разработчик Web <6562...@gmail.com> wrote: > > JIT I've had this solved, not only the application, but a way to. > > Am sharing my experience without labels "bad", "cood", "truth" or "correct", > like you did. > > Your arguments are based on your principles and I don't see in your words any > point to discuss, so - use pm or share here secret of error-free code, if you > have ideas how to solve "my" application if "you know what is the correct > design". > > I think the people who use labels usually never share their experience.
I already shared my experience - to use PHPStan with the highest level of assertion to catch a lot of errors, warnings, and possible issues in the code and fix them before the code even runs on a server. Did you read my message? Did you try PHPStan? If you tried, what was the result? Please share it. When you say SOLID prevents from solving business needs quickly, you should know that business always needs everything yesterday. The problem is not in SOLID or PHP language. The problem is in a bad design/architecture that led to a lot of errors and warnings in unpredictable places that require super custom collection of them on EVERY request. Properly designed applications do not require language-level changes to fulfill business requirements and monitor edge cases. If you have a super legacy code, why the language should care about it? Is it the purpose of the language? Just drop this legacy code if it requires custom error and warning collection. Explain to the business that the code state is so weird that it requires a lot of time to refactor or to reimplement it from scratch. This is a very common problem of legacy rubbish code and it is not specific to the PHP language. Switching the discussion to a flame with personal offense is not a good style here, please don't do this. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
