Removing Python 2.x support from Django for version 2.0 • Hacker News Board

Re: Removing Python 2.x support from Django for version 2.0

#411

Post by 72deluxe » Wed, Jan 25, 2017, 10:17 AM UTC

lmm wrote: post #272

72deluxe wrote: post #260

Earlier quoted context omitted.

Just use C++ and your Qt bindings will never go away!

Qt is a point in C++'s favour, but not enough to outweigh the downsides of the language.

What! There are no downsides to the language! I jest

I love catching errors at compile time, not runtime :-)

Plus, it runs faster

Re: Removing Python 2.x support from Django for version 2.0

#412

Post by JCzynski » Thu, Jan 26, 2017, 3:50 AM UTC

djsumdog wrote: post #368

JCzynski wrote: post #271

Earlier quoted context omitted.

I suspect Python 2.x will be extended like copyright.

I doubt it and that argument makes no sense. Copyright is extended thanks to the lobbying effort of huge business like Disney in order to make a ton more money. Unless you see some big corporate support contracts coming over the horizon for PSF, not to mention they'd have to be worth the money vs the technical debt, I don't think Py2 support will get extended.

Backlash from the tons of big companies still using it will become lobbying to keep it supported. I don't expect them to stop in the next couple years, or the next few, etc.

There's less muscle behind keeping Python 2, but there's a lot less muscle needed to keep it going than to extend copyright.

Re: Removing Python 2.x support from Django for version 2.0

#413

Post by lmm » Fri, Jan 27, 2017, 1:59 PM UTC

72deluxe wrote: post #411

lmm wrote: post #272

Earlier quoted context omitted.

Qt is a point in C++'s favour, but not enough to outweigh the downsides of the language.

What! There are no downsides to the language! I jest I love catching errors at compile time, not runtime :-) Plus, it runs faster

I like catching errors at compile time. But C++'s unchecked manual memory management introduces more errors than the rest of the language eliminates, undefined behaviour turns all bugs into security bugs, there aren't first-class sum types (std::variant is finally on the way in but seems quite restricted; std::visit, while much better than what came before, is pretty cumbersome), and templates are cumbersome in syntax (and error reporting) and not as safe as they look thanks to partial specialization (which will be fixed by concepts if they ever actually make it into the language, but, well...). Along with plenty of less immediate problems (e.g. the lack of a module system).

If there were an ML-family language with good Qt support I'd use that for my GUIs - I use ML-based languages for almost all my non-GUI work. There's plenty I dislike about Python but it's still the best desktop GUI experience I've found.