2/ One of the most consequential questions was whether to double down on Ruby and invest to let it scale with us (the way FB did with PHP->Hack), or migrate away (the way Twitter did with Ruby->Scala).
-
-
Prikaži ovu nit
-
3/ I was the one largely responsible for bringing Scala to Stripe (for async and batch processing), after seeing how necessary and effective that migration was for Twitter. But I'd also seen just how all-consuming the migration was. Could Stripe's product survive that effort?
Prikaži ovu nit -
4/ We ended up gritting our teeth and recommending doubling down on Ruby for the core API stack. Even though I believed that was the right decision, I was really worried we wouldn't be able to materially reshape the Ruby development experience the way FB had with PHP.
Prikaži ovu nit -
5/ When
@nelhage and others kicked off the Sorbet effort, I was hopeful - it was worth trying - but very skeptical. I shouldn't have been. I'm amazed and impressed by how fully Stripe committed to it and followed through.Prikaži ovu nit -
6/ It's also awesome to see the contributions and adoption from outside Stripe. There's not really a further point to this thread. I mostly just wanted to appreciate what a badass
@nelhage is. /finPrikaži ovu nit
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.