361–370 of 388 posts
He was gracious and polite enough not to call me a dumbass for not realizing that tabs were a requirement, not an option.
That was also when I became a tab-convert.
Thank you Guido for this incredible tool that has helped so many others actualize their solution aspirations.
Did you notice this: "He has already put into motion the conversion of the Dropbox server code from Python 2 to Python 3." Even the company that hired Guido is still heavily dependent on Python 2, and it doesn't surprise me at all; my own employer still has a lot of it in internal tools.
Don't they have source to source compilers that do the migration for you? I don't understand why the friction is so strong with python.
Dropbox's server code base is literally millions of lines of Python 2. The "stop all development" approach simply won't work there. The only thing that works is to port the whole code base to "straddling code" that works on both interpreters, then switch interpreters. Automated tooling to prevent regressions is essential.
Earlier quoted context omitted.
"But it never amounts to anything close to a debate about what language I should use." So if your task was to deliver let's say commercial grade FFT library ( substitute with any other long computationally extensive process ) for consumption by others you would write it in Python?
Simple question leads to downvoting? Looks like we have a knight in shining armor protecting the castle of Python.
Earlier quoted context omitted.
I think it is about the thinking process of the person, I assume you are >35, you grew up at a time that people were think about the performance more than the readability, that was the bottleneck back then. Now that you have bigger systems and more complex requirements and cheap high performance computing, the balance is tipped. And because python is (almost) on the opposite side of the spectrum for your thinking pro…
I assume you are >35, you grew up at a time that people were think about the performance more than the readability, that was the bottleneck back then. From the old fart: conflating performance conscious code with the lack of readability is plain wrong.
Edit: I cannot blame too much though, its generating comfortable revenue for me as a consultant. Still, having to deploy nginx/haproxy to load balance python servers for only 200 requests per second each makes me pray for our planet, but it grants me the money the customer saved on developers ;-)
Earlier quoted context omitted.
I can only dream of a panel or a TED talk with those computing sages! (I guess they are all alive right)
This is pretty close! (Guido van Rossum, James Gosling, Larry Wall and Anders Hejlsberg) https://www.youtube.com/watch?v=csL8DLXGNlU
Did you notice this: "He has already put into motion the conversion of the Dropbox server code from Python 2 to Python 3." Even the company that hired Guido is still heavily dependent on Python 2, and it doesn't surprise me at all; my own employer still has a lot of it in internal tools.
I recently went through this process for the Python portions of our large central codebase. It took a few months but most of that was due to coordinating delivery and careful backwards-compatible rollout to multiple streams and licensees, guiding licensees through upgrading their own scripts, etc. Maintaining backwards compatibility wasn't as painful as I expected, but I'm happy that we got to deprecate P2 support on…
Earlier quoted context omitted.
I'm starting to long for a stack that doesn't constantly change. Just set the features and that's it. Security updates only after that. It feels like a constant grind keeping up with everything. Containers, clouds, programming languages, operating systems, frontend frameworks, transfer protocols, it seems like it takes so much effort to just build something and keep it going. That Python 2 is still around doesn't rea…
Clojure has had only a single backward breaking change since its creation in 2008, it took 10 full years before being introduced, and it was a pretty minor one at that. Java and the JVM themselves value backward compatibility, and I'd say Clojure takes it a notch above that.
Earlier quoted context omitted.
I recently went through this process for the Python portions of our large central codebase. It took a few months but most of that was due to coordinating delivery and careful backwards-compatible rollout to multiple streams and licensees, guiding licensees through upgrading their own scripts, etc. Maintaining backwards compatibility wasn't as painful as I expected, but I'm happy that we got to deprecate P2 support on…
How so? It’s automatic with tox, isn’t it?