#kludges — Public Fediverse posts

No, I do not want to stack more #kludges on top of 20+ years of #technicaldebt to get this working. All over the file system, all different users and groups. Things were less standard then. Things are more standard now. I’m tempted to suggest that we thoroughly #refactor but the application is supposedly on its way out. We need a discussion about #tradeoffs.

All this to avoid some cryptic error about shared memory permissions. I shall #nope out of #debugging it in its current form.

A few of #Python 3 #quirks and #kludges

• Global Interpreter Lock
• Strong, dynamic typing
• Massive \(\texttt{Any}\) hole in the type system
• Verbose class definition
• Declaration of instance attributes is their definitions in \(\texttt{__init__()}\)
• Repetitious \(\texttt{self}\) and kludgy \(\texttt{super().__init__()}\)
• Kludgy string-quotes to reference the class from within its definition
• Kludgy \(\texttt{TypeVar}\) definition
• Absence of structural typing
• Need explicitly to convert iterator to list using \(\texttt{list()}\)
• Usurping the \(\texttt{id()}\) name
• Inner method may mutate referenced objects in the closure but may not mutate primitive values therein
• Kludgy \(\texttt{main()}\) invocation
• Disconcerting lack of type information in the holdover documentation from the P2 days