>>75355659>it's brain damage tier specifically because it's the only language I know that allows you to completely fuck yourself over while being extremely silent about it.You haven't had the pleasure of working with python, have you?
You can encounter a syntax error, or any other seemingly static code error, after dozens or hundreds of hours of runtime, because those errors aren't detected until the application actually tries to execute that segment of code during runtime. Or worse, that code segment might only raise the error sometimes, dependent on input because of duck typing.
And it's not uncommon for python applications to suffer from the same bullshit that constantly plagues java, where people catch exceptions and then throw new exceptions instead of re-raising the exception or otherwise maintaining the stack trace.
>In assembly this does not happen. Despite assembly looking harder, it's much easier to reason about.If you're limited to academics or just making something technically functional, I guess, sure. But when you need to meet a performance target while working within a set of limitations then things can get very tricky, and silently fucking yourself over becomes a lot easier.
