I'm detecting a bit of a trend here.
* Start with python * Find out it's a little horrible. * Hire Guido * Python still a little horrible. * Switch to Go
* Start with python * Find out it's a little horrible. * Hire Guido * Python still a little horrible. * Switch to Go
Much more along the lines of:
* Start with Python
* Have a great time and build successful apps with it
* Become global-scale infrastructure provider
* Hit problems that only occur at that scale and switch tools
The take-away is, you're almost certainly not going to end up at the size of Dropbox. If you're spending ages as a startup futzing around using bleeding-edge technology just because it's cool, you might well be wasting time – or at least prematurely optimising.
This is the perfect example – Dropbox has the engineering talent to write a set of libraries to implement basic features. Earlier-stage companies don't have that luxury.
I don't know about you but its hard to sell upper managers on complete rewrites of things when the end result is: no real change but it might/should/could run faster. Unless performance is a concern to be addressed the risk of changing technology stacks doesn't seem a great idea.
> HN post about any language > Snarky comment about any language > Language war
It's depressing that your comment has percolated to the top of the thread; it has nothing whatsoever to do with the story.
Well, praise for a language is telling people how it suits your needs, so...
>For clarification, Dropbox will continue to develop majority of its features in Python.
Besides that, they're migrating only some parts of the backend. They're not "switching". The rest is still Python.