pekk

Apple IIs were all over US schools for this reason.

Why would I be digging through Red Hat's blog to find this, and not find it on the site of the actual thing itself?

I wouldn't read too much into changes of version numbers. vim was being updated continuously.

All they wanted was to fork the project to "clean up" the code in ways they wanted, manage the community themselves, etc. It wasn't like all their patches were flawless and Bram just wouldn't accept them.

Just dumping any old code into a project the first time it's demanded is a sign not of enlightened maintenance but of gross negligence. It's good if there's a lot of feedback on patches, it's not some kind of aggression.

I can already use the mouse normally in vim... is it that the configuration is too hard?

Devil's advocate - how is it really better to have a bunch of autogenerated Django migration files?

What does PG need to improve, then? I see a lot of discussion of how Oracle is better at this or that but not much discussion on how PG will come to parity and how we'll know when it's finally good enough to use.

It's worse than that. You're not just choosing a reliable solution, or even a solution with a conservative reputation so that your butt is covered. You're choosing a solution which may actually be worse because when you fail to deliver for someone else, you have someone to scapegoat. If there is nobody else to blame, you might take the blame for having chosen open source with no specific party to blame (the hot potato stopped with you).

You can absolutely do string handling in a common subset of Python 2 and Python 3. It won't work for legacy string handling code if you relied on implicit coercion, but then the same apps are unlikely to support unicode either.

FORTRAN 77 is just as likely to be abandoned in 2020 as well. And?

We've already had tools like 2to3, but they weren't all that popular, and this won't be either. Most things are ported to Python 3 now and most new projects just use Python 3. Never fear.

Pigs fly - he already has a draft of LPTHW for Python 3

Those benchmarks aren't any more standard than anything else.

Google produced more relevant results than Altavista. That's about it. They didn't build or save the internet. Without them, search engines would have improved anyway and we'd be just fine. Google was never a charity and we don't have to protect such corporate behemoths from criticism.

Ironic since Ansible's lack of Python 3 support was due to vociferous insistence by key Ansible developers that it would be wrong even to allow the use of Ansible with Python 3 as long as popular CentOS versions did not have it.