Comment by chews
5 days ago
It really speaks to how great the technical team can be. As crazy as it sounds Goldman Sacks and JP Morgan both maintained 2.7 Python as a core language until just a few years ago (yes, it's still used in production).
5 days ago
It really speaks to how great the technical team can be. As crazy as it sounds Goldman Sacks and JP Morgan both maintained 2.7 Python as a core language until just a few years ago (yes, it's still used in production).
https://calpaterson.com/bank-python.html
This is fascinating, thanks for the link. I love to learn about big systems that are developed in the same room where the problem they're solving lives, so to speak.
Too few of these are revealed to the rest of us, as the piece notes. It's a shame, there's lots to learn there. Instead most will be lost to the mists of time, and some dumpster diving digital archaeologist will have to get lucky for us to hear about them.
That was a very interesting read, thanks.
I have run into other large (well known) financial companies on 2.x as well. They were using our old unsupported SDK and some long planned and communicated service API change broke them. They could not update to any recent SDK. I did gently point out their python version was 10+ years out of date.
if anything, it only shows just how bad breaking backward compatibility is - py3 was released in '06, 20 years ago
Or insane
Python is used as a kind of 'visual basic' language in a lot of banks especially in front-of-house trading software, e.g murex or frontarena. Migrations between major versions of these can take years, costs 100s of millions and involve thousands of devs. Mistakes can be _expensive_.
It is kind of 'insane' but also, meh..
There's more dragons out there than we've been led to believe :}
It's a great 'glue' language to tie a lot of systems together, especially when you think of MS Excel as a system.
3 replies →
Maybe the bank bailouts were a mistake