3 ms·
I had a few laughs with this, but (maybe because I have been using Python since 1.2) I just can't relate to the Python bits. I migrated all my "working set" st
by rcarmo 6y ago
I had a few laughs with this, but (maybe because I have been using Python since 1.2) I just can't relate to the Python bits.
I migrated all my "working set" stuff to Python 3 piecemeal over a couple of weeks and never looked back (except when I needed to pick up some older project and take an hour or so to refactor it).
The "There Will Come Soft Rains" reference, however, was brilliant. I hadn't thought of that story for _decades_ and it hit home.
- erichocean 6y ago> I just can't relate to the Python bits. I work in visual effects/animation, and 2020 is literally the first year anyone is even trying to use Python 3 (and Python 2.x) is still supported everywhere. Prior to 2020 Python 3 couldn't even be used at all (and I mean that literally: could not be used outside of isolated toy examples on alpha software that wasn't actually running in production). We (as an industry) have written thousands and thousands and thousands of business-necessary logic/scripts/libraries in Python 2.x that have to be updated to Python 3 that work across commercial tools so literally every tool has to be updated at the same time in tandem to Python 3, so much so that the VFX Platform[0] project was created in 2014 specifically to address how badly Python 3 had fucked everyone in my industry. It's all make-work too: literally none of us actually need Python 3's new features. Javascript's "use strict"; is the way to do backwards compatibility if you really really really need to change the semantics and keep existing code working as-is. [0] https://vfxplatform.com/ https://vfxplatform.com/