Microsoft issues an update: it's supposed to update the updating system for future updates. It bricks phones.
Apple issues an update: Adds a few minor features, fixes bugs, improves web browser performance. It Just Works.

I find the trolling with "mandatory silencing of complaints" ironic since one of the features in iOS 4.3 - a user preference for the switch on the iPad to function as orientation lock or mute - is specifically in response to user feedback.

Meanwhile, Google issues an update. You can't use it until your carrier/handset manufacturer says you can (it took a month for Gingerbread to show up even on Google's own Nexus).

TLDR, etc - but let's just say you follow the advice to not use firewalls in front of your web servers. Those web servers aren't going to load balance themselves (at least, not short of old "www1"..."www16" DNS entries), so the next bottleneck becomes your load balancers. Admittedly, these do tend to perform MUCH better than firewalls, as their routing and inspection tends to be much simpler.

However, the common conception of lots of traffic hitting a bunch of web servers directly is not the right way to think about the problem.

Yes, because everyone who uses SourceForge is on Linux. There is such a thing as open source Windows and Mac software you know.

I predict within six months "OpenOffice" will be dead and "LibreOffice" (or similar community-owned fork) will have supplanted it. Linux distros will drop it like a hot potato, and Novell and IBM sure aren't going to tie themselves to a hostile third-party for their efforts.

First of all, this is just used for pirating purposes. In fact that's the only thing the hack allows, so drop the homebrew bullshit.

Pardon? I have no interest in either pirating OR homebrew. I just want to load the games that I bought onto the console to improve load times, avoid disc damage from handling, and keep all my games available at all times. What's the point of a 250GB drive it all I have on it are dinky PSN games?

Said games are also designed for a mouse, and typically require very precise pointing and clicking, which is very difficult on a phone. Many also require hovering - something impossible on a touchscreen.

The actual notation for anyone beyond pre-algebra is x, and that renders just fine in text.

The use of parentheses here is needlessly confusing - I didn't take it to mean "variable" at first or even second glance. Had the "answer" not been shown, I still wouldn't know what they were asking for with such tortured symbology.

Such reporting wasn't disallowed until very recently. There was a very good reason for it as well - developers then got that data back so they could tell how many people were still on old OS versions, what the uptake was on a new OS, and could plan their features and releases accordingly.

The only reason Apple got upset is it revealed prototype OS versions in their lab as a side effect.

The tethering app wasn't discovered because it was extremely difficult to trigger - it required very specific network settings, a multi-step setup process, and tapping different colors in a specific pattern just to enable the tether. Very different from discovering an app is sending your data off wholesale.

The hidden tethering app is only going to be discovered via thorough code decompilation and analysis. Sending chunks of data to a random server for no appreciable purpose can be found easily via tcpdump.

Amazing what a gets a +5 Informative these days. Adding links?

The first example was due to a developer "hacking" accounts (i.e., guessing passwords).
The second example is the same story as the first, from a different source.
The final example is the only one that holds any water. And that allowing crap apps through, not malicious ones.

Sheepshaver, Basilisk, and Mini-vMac will keep you going on for classic Mac stuff. I actually have a copy of Ancient Art of War on my shelf, as well as a working Mac Plus. However, mini-vMac plays it just fine on my 2010 MacBook Pro.

Interesting how people are quick to jump on Apple for this, when Android and Chrome are created by an advertising company.

They're right, and despite the tone in the summary, Apple's quote pretty much spells out why.

I was also surprised to find that I strongly preferred glossy screens. Yes, there are more reflections, but working indoors - and even with a window right next to me - I really don't see any. Sure, if I actively look, my eyes refocus and I see my lamp in the corner behind me, but it hasn't been anywhere near the problem I was afraid it might be. And this is switching from four years on a matte MacBook Pro to a new glossy MacBook Pro.

Unless you're going to be outdoors a lot, I'd go glossy. Sorry the submitters particular environment doesn't work, but I don't think it will be an issue for the majority of folks.

Don't stop at standardizing the connector - you need to specify wattage as well. Perhaps multiple classes so as not to burden netbooks and low power systems with adapters designed for 17" desktop replacements.

I found out the hard way that you can't use Apple's older 60W adapters with the new Core i5/i7 MacBook Pro's, which come with 85W adapters (the reverse works fine and is fully supported). It used to be it would work, but charge very slowly - a fine tradeoff. Now with the new i5/i7's it confuses the hell out of the system management controller, and makes the system act as if it has no battery at all - it sleeps immediately if the AC is removed, even if the battery is fully charged. I found that out when I packed my wife's MacBook AC adapter by mistake - which is visually indistinguishable from the new 85W adapter.