Right, the 20% boost is unrelated to the Gilectomy.
> though, as Guido van Rossum noted, the Python developers could always just take the performance improvements without the concurrency work and be even faster yet.
Why be 10% faster single threaded when you can be 20% faster single threaded!
I don't think the goal is to "compete on speed", but I'm sure people wouldn't complain about their Python scripts running 15x faster on their 16 core CPU.
And it is also about flexibility. What I love about Python is the simplicity, and let's be honest, multiprocess anything but. Especially if you fall into one of the gotchas (unpickable data for example).
For all intents and purposes, Index and Vive are equivalent when it comes to the game support, so while at a hardware level Index is better (though Vive is about to announce new stuff too, and the Vive Pro is quite competitive with Index), it's besides the point here.
Is that true? From my understanding, Oculus has exclusive games, as well as supporting all open games, so Oculus basically supports all Vive games + a bunch of exclusives Vive doesn't. What games do Vive support that Oculus doesn't?
> It’s not required that you have an account or even use the software
That's the key point. The fact that some people weren't even able to use their Oculus device when FB went down for hours is insane. Imagine not being able to use your mouse or keyboard because Logitech went down.
There's a very big difference between an optional cloud system that brings convenience (settings sync) vs a required cloud system that the device cannot be used without.
From my understanding, the comment about was specifically trying to write regulation against the latter.
Would be ironic since OP caught an exploit that their entire team wasn't smart enough to catch... yet somehow he wouldn't know about something as basic as VPNs?
Assuming you didn't care about the path, could you also take some optimal path where you go east to west to prolong the days, then go west to east to shorten the nights. Could probably play with south/north too depending on the time of the year to get longer days. Or maybe you can go far enough to the pole where it's always day.
> though, as Guido van Rossum noted, the Python developers could always just take the performance improvements without the concurrency work and be even faster yet.
Why be 10% faster single threaded when you can be 20% faster single threaded!