Message from JavaScript discussions

September 2017

— Why would one do this?


Because you concat strings with a . in php. Dont ask me why... Also i'd expect an error and not this kind of working bullshit

— But thats what you get for using php

— Meh, there's worse problems than the semantics, the semantics are just the most noticable thing

— There isn't really a fleshed out language, most interactions are directly with C++ libraries, which aren't even renamed.

Message permanent page

— So what it comes down to is... You'd use the same libraries (std, stl, boost, etc...) but have a better, easier experience by using C++ directly, IMO.

Message permanent page

— Plus you can do type safety, strict/static types easier; a construct that when tried in PHP is annoying at best, catastrophic at worst.

Message permanent page

— Https://

— Duck typing isn't a problem, inconsistency is objectively bad always.

— That is the number one reason it is considered objectively bad... If I were speaking subjectively I would say so and you'd know it's a matter of opinion, which this is not. Compared, objectively, to the very languages PHP was based off (semantically, even), PHP simply *is* far worse in terms of consistency. There is no other real metric than "is it on fire?" that would draw such a conclusion

Message permanent page

— Looking at the question another way, one could say a cart with wheels at random 20 degree angles is "objectively bad" because the ride is very rough, but it still gets the job done at the end of the day.

Message permanent page

— It could be the highest performing language in the world, with the best polished code ever inside it... But if the only interface the user has to interact with the code is a bad one, it doesn't matter how good the insides are.

Message permanent page