Mark Shannon's involvement is more interesting. There is no evidence Guido will be especially good at optimizing CPython performance (and arguably lots of evidence to the opposite). And as he's no longer BDFL it's not clear what power he really has to get his changes in if the Steering Council still shares his previous aesthetic preferences and not his current ones.
Guido track record speaks for itself: he gives an announcement, he studies the problems, he implements, he releases something that kinda works but is meh, he improves on it for years, and then you have a new python feature.
He always delivers. That's a trademark.
So yes, it's a big deal. It means something will come out of it no matter what, in opposition to everything that happened before.
I have absolute trust in GvR's decisions in many areas, particularly about language design and teaching programming. But I don't see that he has any special insights into VM performance, let alone the low-level intricacies JIT design.
As mentioned elsewhere in the thread he really has egg on his face after denying Python's performance problems for so many years. I would have more respect if he had taken a firm stance that keeping CPython's interpreter simple had pedagogical value, but instead he (and other core devs) repeatedly argued that Python did not have a performance problem, and that's why it was OK to keep it simple. It took until major pref regressions early in the Python 3 lifecycle to break out of this mindset.
> But I don't see that he has any special insights into VM performance, let alone the low-level intricacies JIT design.
The guy had no insights into language design before creating python.
He also has Mark Shannon, has the entire MS team available on the phone if needed (including the .net team, with stellar JIT), time and a good brain.
> As mentioned elsewhere in the thread he really has egg on his face after denying Python's performance problems for so many years.
He spent 20 years maintaining a project with minimal resources, so you have to make hard choices on what to work with. Perfs were not the objective of Python, and for the majority of the use cases of the time, it didn't matter much.
Now that more important things are sorted out, like unicode handling, and that Python 3 is a smooth running project, he is been given the opportunity and resources to work on the problem, so he does.
Good for us.
Honestly, for me perfs are still NOT a priority, I'd rather him work on bootstraping, but I'm glad and excited that something good will come out of this.
> The guy had no insights into language design before creating python.
Well, except for working on ABC for years, right?
> He spent 20 years maintaining a project with minimal resources, so you have to make hard choices on what to work with... Now that more important things are sorted out, like unicode handling...
I don't see any evidence of this being GvR taking undeserved credit rather than it just being another of the weird cults that 4chan has built up around major programming figures from the late 1990s.
> Why do people in the Python community get so excited over announcements?
When you like a tech, knowing people are brewing improved perfs on it is kinky. On Python, the motto has always been "it's fast enough", "if you want perfs, don't use python", "C extensions will solve this", "we don't want to make the main implementation complicated", "python dynamism and GIL make it a hard problem", etc.
So in the python world, it's particularly big news, especially given that previous attempts (gilectomy, unladen swallow, first pyston...) all died.
> So in the python world, it's particularly big news, especially given that previous attempts (gilectomy, unladen swallow, first pyston...) all died.
This is precisely the point you seem to be missing. All those things you mentioned were similar big announcements back in their day, and they all have just died by fizzling. What should be setting this one apart?
When Guido was the BDFL (but whom am I fooling, everyone still will blindly accept a PEP from him and his opinion will still weigh a ton, steering council or not), he was pretty actively against any kind of bytecode-level optimization even though a lot could be done that way, citing “simplicity” and “readability”. Most Python core developers have had pretty much a Pavlovian response to shut down any and all such discussions.
I think they could get away with it for a while because none of the competing implementation would readily steal Python’s darlings, namely NumPy/SciPy and Tensorflow. Now there is competition, and it can really push CPython away to being a niche “reference implementation”, thus we are seeing these twitches.
The track record of CPython core team in the last decade makes me very wary when it comes to bringing in such features. Ship it or it didn’t happen.
P. S. Microsoft once threw a large sum of money at Kenneth Reitz to work on Requests, anyone remembers how that story ended?
Reitz is no core dev, true, but he serves as an illustration and a cautionary tale of what can happen if you throw large sums of money at seemingly-prolific people hyperactive on socmedia.
Namely, that it’s absolutely not guaranteed to work.
What track record does GvR have in terms of speeding up CPython? He did not care for 3 decades (which is a defensible position given C extensions) and has been literally called "the boat anchor" by another HN member many times.
Mypy was Jukka Lehtosalo's work, asyncio was fixed and extended by many.
So now he needs a project at Microsoft, he changed his mind (or had it changed under pressure) and this is the project. We'll see, I agree though that the first version will be underwhelming, the following versions will have a max speedup of 50% but will be celebrated at conferences and here.
But I'm dreading that people will start doing it on sane persons that just want an upgrade.
I've read enough Sci-Fy to have a list of 1000 ways it can end badly, and we only need one.
People are dumb enough to get phished by email, gov is spying on any phone, pirates manage to access to nuclear plant, and you want to connect your brain to a network?
I’ll give you a positive counterpoint, my immediate thoughts from the headline alone were “great, finally a decent way to ensure I never suffer from locked in syndrome”, “wonder how invasive it is”, “I’m not in the right mood to even open this link”, and finally a small shudder as I try to avoid thinking about locked in syndrome by starting to focus on other tasks.
Unfortunately, I think the wrong it has the potential to do to the human as a specie outbalances it by an order of magnitude.
It's useless to worry though, we are a careless race, we will use it no matter what, and we will hurt yourself in the process. I just hope it will not be too much.
My hunch is that Rob Pike, Ken Thompson, Russ Cox and the other Bell Labs alumni behind Go disliked GNU getopt-style flags, like they dislike a lot of other GNU and BSD decisions that "contaminate" the original philosophy behind Unix.
This overall attitude has led to many design decisions in Go, which define the language for better or worse. Statically-linked executables, for instance, contributed more than anything else to Go's popularity as a CLI tool language. Of course, the Bell Labs crowd was already highly skeptical of dynamic linking. See Rob Pike's opinion here:
http://harmful.cat-v.org/software/dynamic-linking/
- Innate distrust of all things BSD/GNU meant that the original Go team didn't feel they have to honor the established tradition. Just like dynamic linking, they believed that if there is something that GNU does wrong, they don't need to follow it just for the sake of keeping compatibility.
- Positive experience using gflags convinced the team that the gflags approach (single-dash long flags) is the best one.
I personally think they were wrong here. As Russ Cox himself clearly stated in response to all requests for fixing go flags: there are many libraries out there who implement GNU-style flags. What happened in practice is that most Go developers voted with their feet and chose a third-party flag module (even Google's own Kubernetes is using spf13/cobra). In the end, the Go flags package just ended up causing more confusion and didn't solve any of the problems (perceived or real) with GNU flags.
You can use -- or - as far as Go proper goes, doesn't matter in most cases. I think popular args libraries do that too, but there's a million of them, so some probably don't.
...aaaand it's more than 20 years old, so yeah, that kinda agrees with the point that it took us a long time to stop doing that because it's confusing.