> If this crap had had to compete with anything else in the marketplace it would have never flown. It competes every day. The morass of terrible tooling is ex

> If this crap had had to compete with anything else in the marketplace it would have never flown. It competes every day. The morass of terrible tooling is explained by the reason that so many other nice-to-have resolutions to common problems don't materialize: even though things suck, improving them is a problem for someone else to solve. Anyone who complains about the state of things (or doesn't) and then proceeds to do things the broken way is contributing to the problem. The JS example is overstated. People who are slinging code around with a nary a care for what types the objects have deserve everything they get; if you end up in a situation where x can be either a string or a number or a list and you're somehow freely making comparisons between them, then the problem is on your end, and it's way further up the pipeline than where the equality comparison token appears. FWIW, HyperTalk wouldn't have fared any better[1]: > Data types usually did not need to be specified by the programmer; conversion happened transparently in the background between strings and numbers. Note that this is not a defense of mainstream professional web development. I probably abhor it more than you do. But the problems need to be connected to their source and not misattributed to a popular punching bag just because it's easy to score points that way. 1. https://en.wikipedia.org/wiki/HyperTalk https://en.wikipedia.org/wiki/HyperTalk