Quote:
Originally Posted by teckk
That will change soon.
|
The only thing I like about the change is that soon this pythonclock FUD will end.
Microsoft and Google have spent years making Python more corporate. You like it better? Alright. You kick it out of the mainstream distros? Whatever.
I strongly prefer Python 2, I already made a crappy Python 3 version of my favourite project, which I've abandoned for a newer Python 2 version, and these people trying to fool people into thinking they have no choice keep forgetting PyPy is a thing.
And not everything people use Python for needs more than PyPy at all. I don't know if it will fix Calibre.
It's stupid. I knew a Nokia dev who still prefers Python 2. You enjoy your brittle string encoding. I prefer real strings. There are some highly technical discussions about exactly how Python broke strings. I don't care-- it's a tool.
You want to deprecate handsaws and be sure everyone switches to table saws? Have fun storming the castle. It's shill work, but 90%+ of the (rather sheep-like) community is with you, you'll be fine.
"Meh" doesn't even begin to say it, but yeah, count another "Meh" right here. "Meh" on a neon sign.
Just to bring things from the People's Republic of PEP back to reality, I wonder if raku fans will treat Perl holdouts with the same indignity and one-sidedness. Python 3 is becoming almost like a different language. Historically, this sort of thing doesn't always help long-term. PyPy works for me.
Oh, and they moved the date again, LOL. Every time they do that, it's like saying "heck, this wasn't quite as trivial and practical as we thought!" Ya think? Compatibility would be easier than this, but they know best. I LOVE people who always know best. They're just the best!
