In this, I completely agree with you.

Do you seriously want to have apps that seem to hang for 2-5 seconds every time a button is pushed just because it needs to save its state before it enters a new one? Most phone apps do not do anything where they need to have their state saved from one moment to the next. The only times you want to have an app continuously saving a file is if it's editing a local document of some kind. If you do happen to have an app that needs to keep persistent data from instance to instance, that's what the OnPause() or OnStop() methods are for. Then this data can be loaded back in when the app regains foreground by using the onResume() method, or regains visibility by using the onRestart() method.

Seriously, read up on the Activity Life Cycle so you can begin to understand what you're talking about.

My post was about what happens when the Phone App takes over. In my development experience, when the phone App takes over, the apps don't always get to perform the OnPause() or even the OnStop() methods before they go straight to OnDestroy(). Having the app actively listening for the phone call event (which occurs about 2 seconds before the phone system activates the phone Application) will give your app an extra bit of time to get the app state saved and properly stopped before the memory manager starts performing an aggressive cleanup to make room for the phone App (this is especially true on low end phones that don't have a substantial amount of application memory to work with).

In fairness, while Location is completely optional and generally unnecessary unless the app is designed for the user to make use of the location data, it is generally a good practice for apps to watch for phone calls just so if there's one that comes in while you're performing $(menial computation X), the app state can be saved to storage and the app suspended so if Dalvik decides it needs to free up the memory resources in the middle of your call there's still a way for the app to recover where it was in its calculations. The reason you want your app monitoring the phone system instead of trusting that OnPause() is going to get called when a phone call comes in is simply that you cannot trust that the Phone App will not cause Dalvik to simply destroy the app instance without allowing calls to OnPause() or even OnStop(). This is especially true on lower end phones that don't necessarily have the memory to spare to run apps in the background when the phone, a memory hog in itself, activates.

I have no problem with having a HUD on glasses. As a biker I could think of many uses of such (a HUD on my visor would be very nice for reading speed/gear/tach/general status without looking down at my gauges, as well as nav). My question is, why does it need a mounted camera too? As a biker, I could make use of a camera rear mounted on my helmet to use as a wide angle rear view. I could also make use of a wide angle feed coming off my front fender to get a different perspective on the road. But to have a feed coming from a camera mounted right beside my own eyeball would be roughly useless. When you need augmented reality or facial recognition or such, sure, attach a camera to the rim; but take the bloody thing off when it's not necessary for what you do.

It's all a matter of taste and what we can relate to. I've not been able to get into any of the Gold Age stories that I've found, and the Silver Age still tends to have too much camp. Being a child of the 80's and teen of the 90's I guess it makes sense that my tastes tend to travel along the trenches of the Bronze and Modern ages.

You fixed nothing and came off as either a pedantic or misinformed troll.

The person I replied to, mvdwege, happens to be the OP that asked the initial question and has very much stated that the partner in question is a woman in the statement I replied to. If you got yourself a /. account and lowered your threshold to 0 you'd see it since mvdwege has been inappropriately modded offtopic, but here's the text of the post for your reference:

Re:Recommend that you keep reading /. (Score:0, Offtopic)
by mvdwege (243851) Alter Relationship on Tuesday June 10, 2014 @06:16AM (#47201357) Homepage Journal
As it so happens, the partner in question is a woman. But thank you for your completely pointless misogynie.

Have you tried asking your partner what she'd recommend? You don't seem to have the experience with comics to realize it, but your question is extremely loaded. There are so many threads from the Golden Age that you could start reading about and reading through a particular thread and it may wind up having no relevance to what your lady likes. Is she into Dick Tracy? Classic Superman, WonderWoman or Batman? Submariner? Human Torch (not to be confused with Johnny Storm from Fantastic 4)? If you talk with your partner about what she likes from that era, she may be willing to open up to you more and start to take you under her wing.

On the other hand... if she looks at you with a highbrow "you're not worthy" sort of look and seems to be annoyed with you learning this world, she may want to keep this world to herself for her own private enjoyment.

Just as much as if the admin password was "toor", "god","dog","password", or "openSesame". A hack is still a hack even if it doesn't require a high level of skill. The skill required to successfully pull off a hack (and not get caught) only contributes to the degree of warm fuzzies a hacker would feel. It does not change the fact that it is a hack.