3 ms·
Your comment reads as "I like ruby therefor php is dumb" > Is performance that much of a big deal for most people? Yes obviously. Performance is important no m
by dangerface 7y ago
Your comment reads as "I like ruby therefor php is dumb"
> Is performance that much of a big deal for most people?
Yes obviously. Performance is important no matter the language.
> the counter-intuitive behaviour of '=='
You should learn the languages type system instead of assuming it works how you think. Again this is true of every language.
> I assume that these obsolete functions and operators still linger for backward compatibility? If so how do you avoid them?
The built in linter gives you a warning that its obsolete.
The inconsistent naming and arguments. Dumb defaults and thousands of functions in a global namespace is the real problem and there is no solution to it. Oh and calling functions is unacceptably slow, that they can and need to fix the rest of this is just I like my language better.
- simias 7y agoI haven't used Ruby in about a decade and I was never a fan. I used it as an example of a technology that managed to become popular despite abysmal performance. I think that's proof that in many situations, especially for web development, performance is a very secondary concern. > You should learn the languages type system instead of assuming it works how you think. Again this is true of every language. A good language should have good ergonomics. Criticism that `123 == "123foo"` is not reasonable cannot be brushed away by claiming that users should RTFM (although arguably in this case it's less an issue with == than "123foo" being implicitly cast into an integer). Maybe this has been fixed and is no longer relevant though (I'm citing the Fractal of Bad Design page).