3 ms·
You’re misrepresenting what’s being said in this talk (the relevant part of the talk is around the 15 minute mark at : https://youtu.be/XzAupUHiryg https://yout
by krstf13 4y ago
You’re misrepresenting what’s being said in this talk (the relevant part of the talk is around the 15 minute mark at :
https://youtu.be/XzAupUHiryg https://youtu.be/XzAupUHiryg ).
The tldr was that they had patched some of the library code without considering the ramifications of the change. At no point in the talk is it said that “switching to Phoenix was a bad idea”.
Also, none of the issues they talk about are related to the lack of static typing.
- Liberonostrud 4y agohttps://github.com/laravel/laravel/pull/6010 https://github.com/laravel/laravel/pull/6010
- krstf13 4y agoSo? Laravel uses type hinting, ok. This has absolutely nothing to do with your previous post grossly misrepresenting a talk. You hadn’t even mentioned Laravel in it. Type hinting is not equivalent to a static type system, which is what the parent was asking about. Finally, in either cases, it changes nothing to the fact that the pain points mentioned in the talk were not caused by the lack of a static type system (which is not to say it cannot cause pain points)