3 ms·
Likely explanation: Not updated in a while and mostly meant for internal use, where developers will mostly interact with Google's legacy systems. I'd also take
by blattimwind 9y ago
Likely explanation: Not updated in a while and mostly meant for internal use, where developers will mostly interact with Google's legacy systems. I'd also take a guess here and suspect that Google might have a larger than usual share of 2/3 incompatible code (binary-text-boundaries are notorious).
- andrewstuart 9y agoIt's a public facing resource that positions Google as being out of date and backward looking.
- blattimwind 9y agoPossible veracity aside, that's largely a problem of their PR department.
- dwringer 9y agoThat certainly appears to be the perception they've created with many. I don't see it that way entirely, because it seems like any programmer using Python will have to come face to face with the intricacies of how Python 2 and 3 differ. If they write all their projects in Python 3 they may never feel comfortable approaching legacy codebases, but if they start off in Python 2 they're going to be peer pressured into learning 3 as well, and get experience with what goes into porting from one to the other - I'd consider that an invaluable lesson.