Ph0X

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.

> more game support

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?

I think you just missed the entire point of the comment you replied to...

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.

is 10$ the cost the customer pays, or the cost of the delivery? I highly doubt the little electricity (or maintenance cost over time) is 10$ per delivery.

Also, as a straight comparison, drones are faster, scale better and are able to work at hours humans wouldn't. So even if it was 5$ vs 10$, some could argue that it's worth it. Obviously not in all situations, but sometimes there's an item you need right now and not tomorrow.

Again, not to take away by the amazing feat Tesla has achieved, but Google has had similar videos going back 2-3 years, and they are still not ready to release.

So either the problem in practice is much harder than a simple video can show, or something else is up.

Though, I think the real issue is that google wants to go straight for L5 (meaning 100% automated, and you can remove the steering wheel). As compared to an L4, which is more like 99.9% automated, but you still need steering wheel for those rare edge cases.

I still finding it silly that they are trying to go straight for L5 (which is the only case where you can fully remove the steering wheel).

By the sound of it, they already have an L4 going (can drive itself in 99.99% of the situations, might need user take over in very rare cases).

Why not for now release an initial car with L4, and collect pile and pile of data, which is what they need to get over that last 0.01%.

Yes, I believe they have an L2 but are working towards and L4. Google is still going straight for L5, which is the only case where you can fully remove the steering wheel. It's a huge bed, and a bit silly, honestly. I feel like at this point, they've definitely got L4 down.

L4 basically says the car can drive itself without attention in most cases. Driver only needs to take over in extreme cases where the computer can't figure it out (something on the road blocking, sever weather, super abnormal situation).

I think they explicitly say "simple merge conflicts" in the title. At the end of the day, you should use your own best judgement for when this is useful, and for when you need to go back to your workspace. It's most definitely not meant to be used for every merge conflict.

But not everyone is working on big projects with tests, and not every merge conflict is actually complex code modification.

Sometimes it's just two commits adding something at the end of the file and there's not real conflict, or maybe you modified the same line twice and forgot to pull before doing your 2nd edit.

It is, but slack seemed to go for a more corporate angle (along with Microsoft Teams), and there's not really anything for more casual users. On the other end of the scale we have Skype but that's more for personal chatting and their group conversation support is very week.

They have found a pretty good niche with a lot of users. Just like how reddit did with subreddits. There are a lot of "smallish" communities out there, based around games, likes, twitch/youtube channels, etc, and they all need some place to hang out when they're not in saig game/channel.

I think right now what matters most is who comes out winner with the biggest community, monitezation can come later.

The part that's surprising to me is how instantly popular of a startup it became with so little information. Was this "demo" they gave so damn good that all the investors (some really reputable ones such as Google) started throwing money at it, without doing their research to see how real it was?

Sounds very suspicious to me.