Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
Windows phone already has 3 times the marketshare and is growing. BlackBerry is dying
Universal apps are what might make or break Windows phone 10.
The OS really is good. It is light, intuitive, and bug free. With no apps and a requirement for developers to write to 2 different operating systems with niche market shares hurt both.
Streaming over the internet is okay, but it's SO dependent on your connection quality (and your bandwidth limits). It can work, though, obviously.
Maybe it'll work in the future, but it's a pretty poor experience right now.
I have the original NVIDIA Shield, the one that looks like a 360 controller with a screen strapped to the top. Late last year they announced a free trial for their GRID cloud gaming service. One caveat was that their servers were all in San Jose, and if you're too far it warns you. I tried it from my home in Illinois, and it was predictably horrible with just a ~70ms ping. I tried it again from California and it was only slightly less horrible with a ~20ms ping.
Driving games become drunk-driving games. Another driver comes in and hits you? Good luck recovering. Forget that there's a turn at some point in the track? You'll never react to it in time. Things that require constant micro-adjustments like drifting are virtually impossible.
Fighting games become button-mashers because you can't react fast enough to block or counter-attack.
Seriously, these were launch titles! I assume 99% of testing happened with local-network latency. If I were the guy at NVIDIA who okayed go-live, I'd be deeply embarrassed.
The only thing I'd use it for right now might be a turn-based strategy games, or other things where latency really has no effect on gameplay.
Google forked their own version of SSL called Googlessl. My guess is chrome would use this.
The big question is Googles implementation based on openssl or libressl? The bug might still be there if former
I'll tell my Mom to type that in a terminal right away.
Not only that, they're probably not naive when it comes to this sort of thing. They know that if they don't want to be liable, they have to operate at arm's length from the data. Not only will they be able to tell their customers that they don't snoop, they're never on the hook legally for what their customers are doing because they're not involved.
I would say 98%
I have never heard of one who doesn't. One client still uses punch cards. if it ain't broke don't fix it!