@iwein @squads @jbqueru Honestly, I'd be a lot happier revitalizing old but perfectly Fortran than trying to keep up with the infrastructure and fashion hell that is Python. I put in the effort to understand the limitations that previous generations of devs were working around - resources, language features, state of knowledge, etc. - as well as the idioms of their workarounds. Often the underlying engineering or science embodied by these codes is still relevant and sound and the codes themselves have been used long enough that most of the frequent bugs are gone. Most legacy code I see isn't bad, it's just inconvenient and few want to put in (or pay for) the effort to refactor and modernize. If there's no money to maintain the existing code, why does anyone believe there will be money to rewrite, re-debug, and document a new code and ensure it will be maintained so we're not going through this same nonsense again in 10-40 years?
=> More informations about this toot | View the thread | More toots from arclight@oldbytes.space
=> View iwein@mas.to profile | View squads@mas.to profile | View jbqueru@fosstodon.org profile
text/geminiThis content has been proxied by September (ba2dc).