Re: New BPCSharedComponent.dll
@Munawar, there are reasons for that. Python 2 has a lot of issues, notably the fact that it has a ASCII and UTF-8 string. Du you like typing u'this' and u'that' in your code everywhere? That's extra boilerplate. So no, not much of a true advantage with Python 2. With python 3, yes you have to do .encode() and .decode(), but really, that's not much extra work, though it can bring in some interesting lines like:
base64.b64encode(b"ffffff".encode()).decode()
And really, C++ would've been a lot harder. Also, I believe your idea that Python is of the philosophy of "It just works" is incorrect. Remember the Zen of Python:
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
Of course, the definitions of "complex", "complicated" and so on are not explained, and are up to the interpreter. My question for you is this: if hundreds of thousands of other people can handle that extra boilerplate, as you put it, which really is just a small -- a very tiny, really -- price to pay, why can't you? What exempts you from also paying that tiny price? Once Python 2 reaches EOL in 2020, it will no longer receive security updates, bug fixes, and so on. You can already understand what that means. Hell, I doubt Python 2 will be offered in downloads for Python any more after it hits EOL, even in linux package manager-based systems like Debian or Ubuntu. Technology is changing, and your only option, really, is to go with it or get swept away by the ocean of change. There is nothing you can do about it. Staying behind on an old version of Python because you don't like the features that Python 3 is making (which, really, I can't fathom) is akin to holding onto a cliff by your fingernails -- one of these days your going to lose your hold and fall to your death.
A few days ago I wrote a Python monitoring command-line client for Syncthing. Its capable of monitoring any syncthing API endpoint, provided the URL and API key, and will check for upgrades as well, use device names instead of IDs, and so on. In it, guess how many .decode()s and .encode()s I used? Absolutely none. And this program is made of 273 lines of code, and was all written in one file, and uses the urllib.request, time, json, sys, os, os.path, textwrap, shutil, threading, datetime, and socket packages.
-- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
