4 ms·
I've used 2.* for about 10 years, quite happily. If I switch to anything, I'll probably switch to Go. (I originally typed 2.7, which is nonsense.)
by trentlott 13y ago
I've used 2.* for about 10 years, quite happily.
If I switch to anything, I'll probably switch to Go.
(I originally typed 2.7, which is nonsense.)
- danohuiginn 13y agothat's quite an achievement, considering it was only released 4 years ago!
- muyuu 13y agoWell, the 2.x branch has been rather gracefully backwards compatible for many years. Even the jump from 1.x to 2.x was largely "assisted". Personally, for me switching to 3 is a massive hindrance and probably I'll never do it. For the kind of things I use Python, the changes are extremely significant and it actually seems to me like a step backwards. It may be an improvement in other respects, though. I don't know.
- bsg75 13y ago> If I switch to anything, I'll probably switch to Go. I think this is what is often happening, given that Go is attracting more Perl/Python/Ruby types than its original target audience of C/C++ developers.
- kazagistar 13y agoRewriting your code base is easier then fixing it for 3? That really just sounds like you are being overly dramatic, or looking for an excuse to try something new.