← Back to all tweets

Tweet by @rauchg

View original on X

When Google App Engine came out (2008), its runtime was a strange "subset" of Python. You couldn't bind to C libraries, open sockets, run background threads… To fetch data you had to: πšπš›πš˜πš– πšπš˜πš˜πšπš•πšŽ.πšŠπš™πš™πšŽπš—πšπš’πš—πšŽ.πšŠπš™πš’ πš’πš–πš™πš˜πš›πš πšžπš›πš•πšπšŽπšπšŒπš‘ πš›πšŽπšœπšžπš•πš = πšžπš›πš•πšπšŽπšπšŒπš‘.πšπšŽπšπšŒπš‘("πš‘πšπšπš™://…") When AWS EC2 came out (2006), you could do ✨ anything ✨. Over time GCP realized that the restrictions did not make sense, and that people wanted to have full control and versioning over their runtimes. They didn't want "Google's Python", they wanted Python. AWS in the meantime accrued an insurmountable lead. We're now, strangely, seeing the same play out with JavaScript runtimes today. I fully expect the "VendorJS" days to be numbered. Save this tweet.

340
Reply