4 ms·

>Sure, just as much as any other language. Did you see the thread I just linked? https://www.reddit.com/r/PHP/comments/41bm7j/new_rfc_allow_specifying_keys_in

>Sure, just as much as any other language. Did you see the thread I just linked? https://www.reddit.com/r/PHP/comments/41bm7j/new_rfc_allow_specifying_keys_in_list/cz1novq https://www.reddit.com/r/PHP/comments/41bm7j/new_rfc_allow_s... I don't see something like this happening this in any main stream language. That example illustrates one thing very clearly. How you believe you KNOW the language, and how it pulls the rug from under your feet in the most unexpected way. You can wait for it to happen to you. Or you can learn from the experience of others. Your pick.

busterarm 10y ago
There's always some "here be dragons" area/library in any language. I've had it with Ruby, JavaScript, Clojure, Scheme and PHP. It's really easy to pick on PHP's array methods. Sure there are problems there. What that means though is that when I'm using them I refer to the documentation frequently. I do this anyway, with any language. The language never made or broke any promises to you, except where the specification is incorrect. Create a ticket when you find it. Notice how in the example you linked that the documentation is explicit about that caveat. Programming languages are just tools. They are not your girlfriend. They are not your religion. There is no one tool to rule all tools and you're not entering into some major commitment in life to use them.