Many languages used [] [... for ...] array lookup (array[0]), adding pointless complexity to the language for very little benefit – as such built-in syntax usually becomes dead weight a few years down the road, as the preferred choice of data structure implementation evolves.

Yeah, I feel like arrays as a data structure have been pretty consistent for a really long time, and their syntax hasn't changed much? What syntax would they prefer, getters and setters?

Like, I get the first part of their point. I just recently implemented a parser for part of the C++ spec, and yeah, there are shift/reduce conflicts when you see <<, because it's not immediately clear whether it is the bitshift operator or the opening of a nested generic. But, I've never heard anyone else complain about brackets for array look ups, especially without offering a preferred syntax.

I was confused about that part too. Maybe I'm misreading, but it seems to imply that square-bracket array lookup syntax is pointless and complex? Either way, IMO, <> is better for generics because it's visibly different than array lookups.