> I don't think it's quite fair to throw this much shade at Python when Ruby hasn't really addressed any of the things that makes Python so popular My issue is

> I don't think it's quite fair to throw this much shade at Python when Ruby hasn't really addressed any of the things that makes Python so popular My issue is that most companies using Python probably don't need the Python-only libraries. Aside from the fantasy AI point I originally mentioned, I think Python is the PHB's choice (like the mauve database) because that's what they've read in or heard in their circles, or because the first person building the webapp wants Django's built-in admin interface (which always becomes a problem later, like apps in Excel become problems later). > Rubocop Yes, it is fairly standard. And I dislike it like I dislike Black (Python's PEP8 dominatrix). Although Rubocop goes well beyond by giving you often helpful advice about optimization choices or unnecessary code. I like it for that, but I want to format in a more column-oriented way than Rubocop or Black allow (without config mods). Black is a horror show to me. It's almost like it was designed to chew up as much vertical whitespace as possible. It's not as bad as PHP norms, but it really does like to turn pleasant tight blocks into twice as many lines and extra ( ) (out of necessity, since Python can't deal with linebreaks well).