[sodality2]

Wow. This is surprisingly good

    AITA for spamming "rewrite it in rust" on Python-based Hacker News submissions?

    NTA - Have you considered posting a guide to improving the Python ecosystem on HN? There are a lot of people who would be interested. There are so many Python projects out there that do amazing things. You just have to find them. 

    YTA. 
    If you want to learn more about language design, statically typed languages are actually a very good place to start. They make it much easier to determine what went wrong when things go wrong - and they tend to have better support for teaching people new concepts through formalized documentation and examples than dynamically typed languages where the only thing stopping you from writing an incredibly broken program is your own understanding of how what you're doing interacts with other parts of the system.

    NTA. I'm a Haskell programmer. I once had to do some emergency backend scripting in Python for a project, and it was a miserable experience. I don't think I've ever written any Python code that I'd call "clean" since. I've heard the same complaints about Haskell, so I'm not sure if it's just the language or if it's common practice to write horrible code that's hard to read and maintain.

    If you want to avoid this in the future, I would suggest either: 

    1) Not doing any back-end work at all, or 
    2) Writing the code in a language that supports prototyping, like Python, then translating the code to Rust once it's complete.