Black/white as bad/good is a clear case where there is a clear logical reason to change IMO. That perpetuates unconscious bias.

And yet there’s a big push to rename git “master” branches, which have no slave connotations and are more analogous to master recordings.

Its not like I’ll fight it, but it’s stupid.

You do? Because I don’t. There is nothing racist about the concept of master. Is a masterpiece racist? Are master tapes, Are post-graduate degrees racist? We may as well declare “work” insensitive because slaves had to work.

Don’t get me wrong, there are many terms we should adjust. I just can’t see how “master” is one of them.

deleted by creator

Why make fun of it though? If you make typing and being checker-clean mandatory on a Python project, you get most of the benefits of static typing. The biggest hole is if the libraries you’re using aren’t properly type annotated. Perhaps I’d feel differently if the meat of my projects was the use of badly or un-typed packages, but thankfully it isn’t.

I would rather have a statically typed language with equivalent clarity, ease of use and extensive libraries, but the benefits of Python along with comprehensive, enforced type annotation are strong. Proper thread handling could be good, but since that forces you towards avoiding monolithic executables, and using asyncio (which is a delight to use), it’s almost a benefit.

Kids often don’t know the difference between “wifi” and the Internet. It’s not an age thing these days.