An oral history of Bank Python (2021)
calpaterson.com
An oral history of Bank Python (2021)
1–10 of 74 posts
Re: An oral history of Bank Python (2021)
#2>Applications also commonly store their internal state in Barbara - writing dataclasses straight in and out with only very simple locking and transactions (if any).
Right out of the gates, it's crazy how this contrasts with Mercury's Haskell infra
Re: An oral history of Bank Python (2021)
#3And I thought rewriting 3rd party packages to work with AFS was crazy
Re: An oral history of Bank Python (2021)
#4What a well-written account of "how things are done".
> Time to drop a bit of a bombshell: the [Barbara] source code is in Barbara too, not on disk. Remain composed. It's kept in a special Barbara ring called sourcecode.
Re: An oral history of Bank Python (2021)
#5Prior discussion: https://news.ycombinator.com/item?id=29104047
Re: An oral history of Bank Python (2021)
#6>Applications also commonly store their internal state in Barbara - writing dataclasses straight in and out with only very simple locking and transactions (if any). Right out of the gates, it's crazy how this contrasts with Mercury's Haskell infra https://blog.haskell.org/a-couple-million-lines-of-haskell/
Eh, to be fair, this post is about a _bank_, and the one you've linked is about _fintech_. They are not even close to the same space, even though they both deal with money.
But also I suppose you may be saying exactly this?
Re: An oral history of Bank Python (2021)
#7>Applications also commonly store their internal state in Barbara - writing dataclasses straight in and out with only very simple locking and transactions (if any). Right out of the gates, it's crazy how this contrasts with Mercury's Haskell infra https://blog.haskell.org/a-couple-million-lines-of-haskell/
Eh, to be fair, this post is about a _bank_, and the one you've linked is about _fintech_. They are not even close to the same space, even though they both deal with money. But also I suppose you may be saying exactly this?
to be fair, it is a fintech that wants to become a bank
Re: An oral history of Bank Python (2021)
#8To the best of my knowledge much of this originated with SecDB/Slang at Goldman - SecDB (securities db I believe) being the object store and slang the somewhat quirky C like language that ran with it (also the only language I’ve used professionally that let you have spaces in the variable names).
Some of the folk that built that (or worked on it) ended up at JPM and Merrill where they built the Python centric version - Alpha and Quartz respectively. Barclays Capital has/had a similar system as well I think, but it’s not one I know about offhand - they did though, memorably, have a system that was pretty much Haskell-in-Excel.
Re: An oral history of Bank Python (2021)
#9Weirdly not dissimilar from MUMPS systems.
Re: An oral history of Bank Python (2021)
#10>Applications also commonly store their internal state in Barbara - writing dataclasses straight in and out with only very simple locking and transactions (if any). Right out of the gates, it's crazy how this contrasts with Mercury's Haskell infra https://blog.haskell.org/a-couple-million-lines-of-haskell/
It sounds pretty similar actually. Barbara fills the same role that Temporal is doing at Mercury.