While not entirely the same, the Galaxy S5 here in the states has something similar. It only works with a handful of services like the Google Play store, but it can also download items from both radios at the same time to increase bandwidth.
Maybe I missed it, but there appeared to be no references to Windows Chicago at all? The article makes it seem like the START button just appeared out of thin air, not a series of trial and error over time. Check out this document which highlights the evolutionary processes that happened between Windows 3.1 and 95
This is just another case of "Not My Problem" syndrome that too many techs get into. They think their code/tools/systems/whatever must be perfect, and other's are the ones fucking up. Samsung drives went on a blacklist for issuing the commands to them due to this bug? "WALP, LINUX IS PERFECT, MUST BE THE HARDWARE GUYS, even though their devices perform perfectly on other OSes" - and instead now we're left with a bug in Linux that corrupts data until the patch can make its way through the distro channels and pushed out to end users.
But only 20% 100 times better, at the same cost.
Pretty much any technical field requires capslock. I'm a software engineer in the automotive field. Tons of code from 3rd party libraries are all caps, as well as the part numbers I deal with in the automotive industry.
Maybe the reason why capslock is used to little is because... think about it. If my entire post were entirely in caps? Count the number of key strokes. Capslock would be pressed once to enter all-caps mode, and once to leave it. To presses of that key vs countless presses of the letters and a few other formatting symbols. Caps lock shouldn't be counted by the number of key presses any more than scroll lock or number lock. Instead they should be counted by the number of other key presses that are modified while they are activated.
Good thing AMD never has such issues...
As a note: I don't even use the onboard AHCI/SATA controller, as I have a dedicated PCI-E SSD, and this still prevented Windows from booting.
"An operating system might have a shelf life of 1 or 2 years." Unless you're Microsoft with a solid long-term OS. How many people still run XP? How many people still run 7? Why? Because these pieces of software were designed from the get go to be long term solutions. Other companies simply are not willing to make such an investment in keeping their tech around in the same way.
When there is bundled in software like this, money is involved. When money is involved, contracts are involved. With contracts, they should directly stipulate that the 3rd party software companies that have their software included must update their software for the life cycle of the device as a term of being allowed to be bundled in. Since this apparently wasn't the case, the OS bundler fucked up.
and at that, only one of the three games returned... but in a new, horrible fashion. why... the... fuck... do these games... which worked on windows 3.1 on 386 PCs running at 16MHz.... REQUIRE A GODDAMN LOADING SCREEN NOW!? And they're apparently to large/complex to bundle with the OS anymore?
Can we get some ACTUAL numbers instead of just some bullshit article describing some vague numbers? As T-Mobile has already pointed out, according to Ookla (ya'know, speedtest.net and a few other services that provide data to the Ookla database), they come out on top on average in the nation. Granted average doesn't mean they're the best at every given location, but being a frequent traveler, I can easily attest that, no, T-Mobile's network isnt anywhere NEAR that slow at LAX. Also, what handsets were they using and in which modes? While other networks offer LTE server, T-Mobile has both LTE and HSDPA+ if the handset supports it. So which of these two networks were they testing?
SCO Unix runs GREAT inside of VMWare... don't ask me how I know this, as I get back to the server room to beat the shit out of some random OS that isn't performing well... again....
Superior technology and design means nothing. Content means everything.
In the earlier days, Facebook, Twitter, Instagram, and Tumblr (probably countless others, too) all had one huge key feature that G+ missed out on: cross-network publishing. Basically as a content producer, this is considered free content/marketing potential. It takes time to author a post on social media sites. Facebook Twitter have long had a cross-posting system, where you post to one, and the post propagates to the other automatically. Tumblr too can feed into Facebook and Twitter. And Instagram can feed into all of them as well. NONE of these fed into Google+ (do they now? I've not used it in ages, so I don't know). But because of this cross-network sharing, it meant that the cost involved with jumping onboard with another social network as an individual or as a business was an extremely small cost (sign up for the new social network, link to existing, and done, since posts propagate automatically). G+ was an added investment on a per-post basis, and this costs time (and to business, thus costs money).
This, just two hours after the headline of "Remote Exploit On a Production Chrysler To Be Presented At BlackHat"
Seriously though, I'm all for automation, communication between devices, and anything else that can help optimize any system out there (this being the transportation system as a whole, not just the internal computer system within a single vehicle) - BUT we need some serious security and accountability. We've seen serious issues with cell phone manufacturers delaying security updates by months (sometimes YEARS) to handsets. Is this going to be the case with cars, too, which traditionally never even get software updates to their infotainment systems? Maybe now that these systems can impose serious risk of physical harm to individuals both inside and outside the cabin, can we get some mandated government regulation that forces software security updates on a regular basis, that also persist beyond just the first year or two of the vehicle?
TLDR: Let's get this shit security, and continue securing it over time with updates, and I'm all for it!
Serious question: how much of this could have either had been prevented, or restored much more quickly if they were using ZFS with proper parity, checksuming, snapshotting, and sending (backups)? This really is the one-size-fits-all storage solution at this point.