[klibertp]

You can't confuse keys in a hash table with properties of objects. It's not confusing, it's a useful distinction.

Most languages that have both objects and associative arrays (so not Lua or JavaScript) make this distinction.

It's not particularly error prone. You're simply refusing ("don't care why") to learn how to use the tool you're given.

[BoumTAC]

user dictionnary => user["email"]

user instance from a django model => user.email

It is error prone. You're simply refusing to see an aberration.

That's how the language works, but it doesn't mean it's intuitive and easy to understand especially for a language known for being easy to use and understand.

[klibertp]

It's not how the language "works", it's what the language offers.

When all you have is a hash table, or when all you have is an object, you get to refer to keys and properties uniformly - because they are the same thing. When you have both, you refer to them differently - because they're different. That's it. There are some languages where objects and hash tables use the same syntax for access even though they're different things, but... you probably never used any of them, and certainly none of them is in the Top 20 on TIOBE.

I'll kick the venerable HN guidelines aside for a second and mention this: you're being heavily downvoted, all your comments in this thread are in various shades of gray, and many people offer many different arguments as to why you're wrong. Yet, you're undaunted and continue posting - I don't want to break the guidelines that much, but honestly, it reads like trolling. You don't engage with the arguments, you're just repeating the same thesis over and over again, without citing evidence. Why?