Breaking all the Eggs in C++ (2015)

Re:Breaking all the Eggs in C++ (2015) by BeetleB on Sunday December 30, 2018 @03:05PM (#18791025)

>We've got more reasonable, less drastic tools. Maybe push those to be used more efficiently, instead of inviting a new Python 3 fiasco.

Most people I know who complain about the Python 3 transition are not heavy Python programmers.

Migrating to Python 3 was certainly a pain, but not really a major one. The number of developers who fled Python because of this is miniscule. If the Python 3 transition is the poster child of "things going wrong" with backward incompatible changes, I would heartily recommend other languages make those incompatible changes.

[ Parent | on HN ]

Re:Breaking all the Eggs in C++ (2015) by ci5er on Monday December 31, 2018 @09:08AM (#18794516)

Really?

I believe that moving a 500k loc code base qualified us as semi-heavy. And relying on packages that didn't move qualified us as stuck.

Now - don't get me wrong: i/we liked python2. There was little wrong with the language or sticking with it. But please don't think the cost of migration was a weekend of lost coffees.

[ Parent | on HN ]

Re:Breaking all the Eggs in C++ (2015) by mianos on Sunday December 30, 2018 @06:55PM (#18792077)

Personally I don't think this is true.

[ Parent | on HN ]