All good points, except this one, which is a real problem: > Changing it now would mean more work to me.
Why can't someone else do it? It seems like OderWat is almost volunteering. Maybe it would be too hard. But I would love to see you say, "Hey, OderWat. Would you look into adopting full case-sensitivity? If it seems feasible, or if you come up with a workable plan (e.g. a compiler flag to preserve partial-casing, and maybe a warning for similar identifiers), would you submit a pull-request?" In other words, delegate work to other developers. You're doing too much. > > It's cool and interesting, but it makes the language less practical, not > > more. > > That's just your opinion. I'm in the majority, by a wide margin. And note that GoLang has a different novelty, which I think is a good idea: The source code [is fully UTF8](https://golang.org/ref/spec#Source_code_representation). You can include UTF8 characters [in the names of your identifiers](https://golang.org/ref/spec#Identifiers). My point is that the identifier is the identifier. For some reason, you see the "identifier" as an abstract concept, with several representations. You are very definitely in the minority. You're probably right too, but sometimes a good idea is just too far ahead of its time.
