4 ms·
Right, I don't think it's necessarily the people that are _for_ PHP are ignoring the past, it's that the people _against_ PHP are still stuck in it.
by kossae 7y ago
Right, I don't think it's necessarily the people that are _for_ PHP are ignoring the past, it's that the people _against_ PHP are still stuck in it.
- slikts 7y agoThis is a common straw man; PHP 5 and 7 made large strides, but that's because there was so much to fix, and there still is and will continue to be, like lack of first class functions, actual modules, etc. PHP is also unsuitable for persistent processes like serving WebSocket.
- DJBunnies 7y agoRatchet works fine.
- krick 7y agoWhy do you need "actual modules"? I feel that (when PSR-4 is followed) PHP's code separation practices are among the best, especially compared to other interpreted web-languages (Python, Ruby, js). And it's convenient while experimenting that it doesn't really enforce anything.
- slikts 7y agoWithout modules there can be dependency hell: conflicting subdependency versions, unless all your dependencies update their subdependencies in lockstep.
- rawfan 7y agoWebsockets are no problem with Ratchet. OhDear is a high traffic app that uses laravel-websocket (based on Ratchet) with absolutely no performance issues.
- imron 7y agoThey probably still have to maintain systems running PHP 5, and are quite literally stuck in it ;-)