It's a bit of a change but certainly the right thing to do.

My only disagreement with the article is the get/set stuff. I still want to keep something like the old container[index] syntax, maybe container.[index] to indicate that it's a form of access. As long as generics go after names, this would not cause ambiguity.

1. <> is hard to read for humans

Not really. <> is unusually pointy among the brackets and comparisons / bitshifts are used in different places than generics are so I've never confused them.

2. <> is hard to parse for compilers

I guess? Does this meaningfully increase compilation times?

3. It makes the uses of brackets confusing and inconsistent

No. A language that uses () for parameter lists, literals and indexing is much more mentally taxing to parse

nope

Stop using types for variables