- No Rust/Go rewrite
- GC not disabled
- Didn't apply the latest research on k/v storage
Jokes aside, this is the fun parts of hosted software and glad to hear the "things don't have to be so hard" side of things. Hope it continues working out!
- No Rust/Go rewrite
- GC not disabled
- Didn't apply the latest research on k/v storage
Jokes aside, this is the fun parts of hosted software and glad to hear the "things don't have to be so hard" side of things. Hope it continues working out!
I've found devs are always trying to over-engineer complex solutions to dead simple problems. Just let Google do it and get some sleep.
And their reason is because their code is currently Python 2. To avoid some manual code refactoring to support Python 3, they shall rewrite in an entirely different language. So they'll train their entire programming staff in Go and task these new inexperienced Go programmers to do a straight port of their code base from one highly opinionated language to a different highly opinionated language.
They've certainly done an excellent job enumerating all of the very lucrative benefits of a Go rewrite, while ignoring or hand-waving away any of the challenges. It all screams version 2 syndrome.
Who knows, maybe this is a great move for them. I’m only going on their blog post about it. But at minimum they've done a poor job communicating how they've looked at this challenge objectively and without rose-tinted glasses.
They have used Backbone.js [6] and experimented with other programming languages like Kotlin [7].
Read their engineering blog [8] and you will know more and maybe learn a few things.
[1] http://engineering.khanacademy.org/posts/python-refactor-1.h...
[2] http://engineering.khanacademy.org/posts/transaction-safety....
[3] http://engineering.khanacademy.org/posts/upgrade-buttons-lin...
[4] http://engineering.khanacademy.org/posts/goliath.htm
[6] http://engineering.khanacademy.org/posts/upgrade-buttons-lin...
[7] http://engineering.khanacademy.org/posts/kotlin-adoption.htm