I wouldn't put mine to the curb because I'm still playing game titles on the console. Having said this, the world being awash in $100 and less boxes that do a better job of Netflix (AND the others...), it's also awash with devices that with a decent BT game controller or similar can manage just shy of the PS3 titles as well.
It's not a wise move on their part. Google's going to eat their lunch if they do this.
It's still a hack and a workaround there. Just because it works "okay" and it's "easy" doesn't mean the yanking of the functionality in the PS4 isn't problematic. I know I'm waiting for a critical mass of PS4 titles before I contemplate a move- and with GoogleTV or an Android HDMI stick, it became stupidly easy to do the others. It's another box, but still- Sony's not getting me to sign off on this crap and at the rate they're going I might just give the PS4 a pass as well.
There is a reason I am keen on seeing if Valve can manage something with SteamBox/SteamOS/Linux. I'm a bit tired of the BS and lies about this stuff.
The problem with USB MSD is that you can't operate against the store with the OS on the device at the same time the Host OS is doing it. MTP was chosen so that you could do things on the store while the device was able to use it at the same time. The fact that the implementation of the whole notion's flawed (Hey, Microsoft came up with it!) in the manner that it's single threaded (You can only act on a single object request at a given time), is irrelevant to everything. Now, if they could come up with a 2.0 that was multithreaded, and have proper USB IF compliant implementations of the same (MTP is an IF spec, mind...) then it'd be great. You need SOMETHING like it in place- just not what we've got in it's current form.
O_o
What security problems? You can't autoexecute stuff off an SD under Android. The only time there's a security concern (and it's going to be the SAME on the on-device eMMC...) is that you can execute code off of an SD that vendors didn't intend for you to run. That's how people side-load in the first place. They didn't change anything with this little change they made in KitKat and didn't break anything any worse than it was with this change back.
The reason that they quit including SD slots was because they want everything on Drive or similar and it lowered the BoM cost to peel those out. It's not security- quit deluding yourself and everyone else with this tripe.
Openness? Please...lay down the crack pipe before posting. Seriously.
What gets me is why they didn't lead with this to begin with. What they did with KitKat was effin' stupid.
As for Verizon getting their updates out? Heh...you're kidding, right? You'd just bend a 6' digging bar all to hell trying to surgically remove their head. I quit trying to hold my breath on that one when they got a Nexus and promptly treated the damn thing like a red-headed stepchild; and then made it...difficult...to obtain dev edition devices. (Ever thought that maybe a dev wants to be ON your damn network since it's reliable compared to the others, Verizon? There's legit reasons to have root permissions on the phone...even if you don't see them and keep deluding yourself that you're "protecting" the users...)
He should outright sue. It isn't anything except a very high quality micro-CNC machine. It's called a Ghost Gunner because of one of the intended purposes. As such, they just breached agreement on their end without cause and he has cause.
Heh... You sound like you have the same attitude most of my preferred staffing agencies have. Most of them, sadly, don't have this attitude. (For example, I will deal with Oxford International, but they're last option for talking to on things... There's a reason for that, which includes excessively low-balling me on past jobs, offering me just any old gig that they think I might be able to fill, never mind that while I'm skilled in Windows development, I flatly DON'T want to do that if I can... And they're just one of dozens I give last chance to or won't at-all talk to/with.)
The agency is supposed to do what you're saying. More often than not, unfortunately, they do what people are posting to on
Entirely too many "headhunters" are eager to get a warm body into a gig so they can get billable hours or get their percentage of the annual salary as a commission/finders-fee for the job in question.
Then there's hiring managers willing to do the same thing to get *someone* in to help them out, regardless because even an ill-fitting posting will move the project along quicker than nobody being there in many cases.
Heh...I've seen both. I will work for the latter, in many cases. One comes to mind, that I won't mention, who'd be on that list. I could do both what he had me doing and the embedded Linux low-level stuff. But...unfortunately, the upper management has this notion that they're better off with Offshored stuff. (Never mind that I had a good time and swiftly un-did the mess they made- and would happily keep it from happening again if they'd hire me and two other devs and not offshore the stuff...)
You should've went for the gold and said... "Being a Glasshole?"
Basically, it was a pissing match like people claim it was. Something that USED to be called out on the carpet over- because it's violating common carrier status that the jokers in question all have and alternately want and don't want. (They don't want the regulation, but they want the shield from vicarious liability from their customers' actions...)
The biggest problem without them is you'd end up having a tragedy of the commons. How would any of them intercommunicate to allow the Internet to be.
One of the things you can do is harshly punish the ISPs in question when they play games like this. One of the things they have right now is "common carrier" status. That's a liability shield against all sorts of things that your customers might do that's illegal. You could be held vicariously liable if you don't have that status and they commit acts of sedition, copyright infringement, etc. You used to run the very real risk of losing that status as a provider of services if you pulled a stunt like this- which kept them mostly from pulling crap like this. We need to bring that back, to be honest.
Because it's been a problem up to this point...not the corporate repository- just about any twit could make an installer/injector that was transparently fire and forget for Windows. Because of the design, it's a bit harder with most Linux distributions whether you're talking about RPM, DEB, or any other packaging system. But, for windows, whether it was GUI or not, it's just simply there. If it wasn't, you wouldn't need AVG/Avast/Avira/etc. or MalwareBytes/etc.
As such, it's a joke. Not liking it? Get Microsoft to get their act together or switch OSes...
If you think the system is working, ask someone who's waiting for a prompt.
