Comment Re:expensive and hard to get (Score 1) 74
Maybe $6 with shipping if you're only getting one, for a 6' cable.
To be fair, though, $10 at a brick & mortar store isn't an awful price.
Maybe $6 with shipping if you're only getting one, for a 6' cable.
To be fair, though, $10 at a brick & mortar store isn't an awful price.
Nothing.
Woe unto any fool who doesn't act with extreme caution when dealing with law enforcement.
Goes for when you're driving, too. In my experience, a cop car is far more likely to suddenly do something dangerous and stupid on the road than the average vehicle. They're worse than makeup-applying cellphone-talking soccer moms. Plus, I assume they'll ticket and/or arrest your ass if you're in a wreck with them even if it was their fault, either because they're just dicks or to cover their ass, or both.
Norway police admit slow response to Breivik massacre
Doesn't say anything about their rules regarding gun use slowing them down, which isn't surprising since that doesn't seem terribly plausible. They fucked up plenty, but not for that reason.
Better look for another example if you intend to hold the same position in the future. Or keep on with this one and hope no-one bothers to Google it again. That works for... well, most people, I suppose.
and real time 3D maps
Whoa, am I the only one who has this 100% of the time, whether I'm using my phone or not?
1) Place kids on shoulders.
2) Do squats
That's a reason why an ICS application wouldn't have a gingerbread counterpart, but not a reason why you couldn't have Chrome on gingerbread.
It's not a reason you couldn't. It's likely a reason you don't.
Gingerbread applications work fine on ICS
Hell, sometimes an app that was fine on 4.x will exhibit bugs on 4.y.
samsung galaxy s
Haha, the Galaxy S, worst thing to ever happen to Android. My S 4G is, likewise, a piece of shit that I hate using, and has guaranteed that I'll be buying an iPhone soon. I can't name a single thing I like about this thing, and if not for barely-usable GPS and web-browsing features I'd have switched back to my "feature phone" with its slide-out texting keyboard and no apps worth mentioning, because that was a better phone than this.
I might, might consider a 4.x Nexus device—Android is quite a bit better in the 4 series—if they'd get rid of the stupid always-on-screen menu buttons. Part of what I hate about my Galaxy are the touch-sensitive menu buttons under the glass which I'm constantly hitting by accident, and now they made that part of the OS itself? There's no way that "feature" was prototyped and tried out on actual users before being greenlit.
Is there seriously anything required for Chrome that isn't in gingerbread?
Man-hours ($$$) to maintain a fork for 2.3 Android.
2.3 APIs and OS behavior are pretty damn different from 4.x.
I ran Win95a (the Upgrade version, even) until eventually moving to 98se. I think I must have had a very unusual experience, but 95a ran better for me than 98se ever did. Way fewer crashes, felt cleaner. Maybe it was the hardware. Good ol' 100Mhz Pentium. All my 98se boxes over the years were faster machines, but maybe the mix of hardware in them just didn't have a certain magic.
Yeah, I'm pretty sure that's either not true, or it was true but only briefly before they abandoned the effort. The only people I knew who ran 2K on their home desktop were geeks, and even those were fairly rare because it had spotty driver support and was sometimes tough to get working on any given Win98-era franken-box—besides, games had a tendency not to play nicely with it even if all the drivers were present.
I worked on a lot of home users' machines around that time and I don't recall seeing a single one with 2K on it. Quite a few with ME when it came out, unfortunately. "Here's Windows 98, but inexplicably slower and more crash prone, and with some config options moved to different locations for no reason. Have fun!" Fuck that OS.
My phone's running 2.3, but it's got touch-sensitive areas under the glass to represent the system buttons, and I hit 'em by accident all the damn time. Add some extra and very much undesirable challenge to Fruit Ninja.
Hell, I occasionally manage to hit the button on my iPad Mini and back out of the book I'm reading or whatever, so I can imagine how much more frustrating a Nexus 7 would be. We've got several 4.x devices where I work, and as far as complaints about the OS from a user's perspective, those buttons are at the top of the list for the guys who have to use them often.
It doesn't help that Android apps tend to be even worse than iOS apps about consistently recovering their state when you briefly pop out of them like that, either.
I'd settle for docs that don't read like they were written by the people who wrote the code, and any attention at all paid to their bugtracker.
Getting rid of the goddamn stupid always-on-screen home and back buttons would be great, too. They're a usability nightmare. Go back to physical buttons, or some solution that doesn't cause so many accidental presses while also wasting screen real estate.
Like most things, it would benefit from being managed by Git
This ea support chat screencap posted in one of the reviews seems worth sharing far and wide, and judging from the way it ends I would guess the owner doesn't mind my posting it here.
If A = B and B = C, then A = C, except where void or prohibited by law. -- Roy Santoro