Oh yeah, that'll be way more convenient. Right up until you need to login when your phone is out of batteries, not in wireless coverage, under water, etc.
I had this problem when I was applying for US citizenship. I was on the crew team in college, which means I had callouses all the time on my fingers, and thus blank fingerpads.
I applied for citizenship 3 times over a period of 3 years, and each time got rejected due to poor quality of fingerprints.
Finally I stopped rowing and then got my citizenship. I'm sure there's some way around it, but it was kind of amusing and frustrating at the time.
You should never give legit answers to these security questions. I just paste in the output of pwgen -s 32 1. This may make your account harder to "recover" but it also makes it harder to steal.
Yes, this is exactly what I do. I have interesting results sometimes;
Bank: I'll just need you to confirm your mother's maiden...um...um
Me: Yes, it's a long string of random characters, want me to read it?
Bank: No, that's ok, thanks.
I feel your pain, slightly, but isn't the majority of this list caused by the fact that Apple's software stinks? There's no way for apps on iOS to share the account details. You don't need to do any of that junk on Android. And you wouldn't have to do any of it on a Chromebook, either.
You don't have to do it on ios either (assuming your using the built-in mail/calendar/contacts). Ignoring that that OP was setting up multiple unique gmail logins (personal and work), the scenario he outlines requires entering exactly 1 app specific password per gmail account in the "mail, calendar and contacts". I have no idea why he's talking about using them in the browser, normal 2FA works fine there.
It's been some time since Apple shipped the X11 package by default. You've had to download it yourself. They're not saving anything by removing it from people's computers
My understanding (and please correct me if I'm wrong) is that an 'upgrade' is really a fresh installation, with your user data migrated across afterwards. In that context it's not really a 'removal' as such -- and it's hard to see how else they'd do it.
I'm actually glad they made this change. In the past, XQuartz was sometimes ahead of the officially distributed version, which could be messy. Now they're the same thing.
Except that XQuartz in the past installed itself to various system paths on Mac OS X. When you "upgrade" the OS the installer moves everything installed out of the way and basically does a clean install of the OS. At the end it copies over everything in paths that it doesn't control (mainly /Users, /usr/local, (/usr/<everything else> gets wiped), /Applications, /opt and others). Anything that is core to the OS will basically be in a clean install state.
For example, I've written some custom device drives for OS X that were installed in the system path (being kexts and all), those were removed. They weren't specifically compatible with OS X Mountain Lion, so it makes sense.
That ad is from 2002. X11 didn't ship with Mac OS X until 2003. Either they never believed in the spirit of that advertisement and the whole thing was a sham, or built-in X11 support isn't actually necessary for it.
Isn't that just because parsing XML in Go is difficult bordering on impossible? Or are you saying there's some other language that forces you to think about XML when you don't want to?
My point was that with Go, I have consistently predictable experience. Its standard library is still not the most powerful across the Zoo, but if it has support of something, I know that I can use it w/o a book "libxml2 for dummies".
