We'll get you a real answer about how the tech stack is today.
But for now I can tell a war story that might be fun. I'm one of the founders, and am in a very much non-technical role now as CEO, I did write a bunch of the very early code (some of which people curse my name for to this day.)
When we were starting, I was limited by how many new languages/frameworks I could learn at once. I started writing the backend in python, because I knew it a bit. But our first writer often needed to use Chinese characters, and in python 2.X I could never get unicode strings to work properly. I couldn't upgrade to python 3, because on google cloud I would have had to learn Docker and I was already learning too many things at once.
Eventually I got so frustrated I threw out several days work and started the whole backend over, with node + Postgres hosted in Heroku. This ended up defining much of the stack we use to this day, which might be good or bad depending who you ask. At least unicode works though :)
I’m curious: what was the issue? I’ve used python 2.7 with Unicode pretty extensively, in a wide range of languages, and have never had problems that weren’t my own fault.
I have memories of the Python compatibility issues causing huge headaches. We're back to using Python due to ML requirements now, but it kept me away for years.
But for now I can tell a war story that might be fun. I'm one of the founders, and am in a very much non-technical role now as CEO, I did write a bunch of the very early code (some of which people curse my name for to this day.)
When we were starting, I was limited by how many new languages/frameworks I could learn at once. I started writing the backend in python, because I knew it a bit. But our first writer often needed to use Chinese characters, and in python 2.X I could never get unicode strings to work properly. I couldn't upgrade to python 3, because on google cloud I would have had to learn Docker and I was already learning too many things at once.
Eventually I got so frustrated I threw out several days work and started the whole backend over, with node + Postgres hosted in Heroku. This ended up defining much of the stack we use to this day, which might be good or bad depending who you ask. At least unicode works though :)