See, this is why I compare it to Python's OSR syntax. People react with these strong responses ("plainly bat-shit crazy"). People focus on inconveniences due

See, this is why I compare it to Python's OSR syntax. People react with these strong responses ("plainly bat-shit crazy"). People focus on inconveniences due to the limitations of limited tools ("I don't want to press spacebar FOUR TIMES at the start of EVERY line of code!"). People come up with elaborate worst-case hypotheticals ("What if you want to share your code with someone using a pastebin service that removes leading whitespace?") that just don't happen in practice. In practice, it's just all upside and no downside. Now I don't need to remember whether it's `openHTTPConnection()`, `openHTTPconnection()`, `open_http_connection()`, `openHttpConnection()`, etc. If I can say it, I know how to type it. Any ambiguous overloads (same name, same parameter types -- which again, really doesn't occur by accident in practice) will be reported & resolved at compile-time. There's no more mystery in this than there is in any function overloading scenario. And in practice, it seems to cause the opposite of holy wars: People realize how pointless all those identifier case-wars are in the first place. There's really not much more that I can say. "In my experience, there's no downside to this feature, only upside."