Yawn. MMO spies figured prominently in Cory Doctorow's "Little Brother" in 2008.
Ultimately, it's nearly impossible to predict market forces and corporate decisions. You made a good choice in both cases based on the information available. There were good communities and significant momentum behind both frameworks at the time. You could post-mortem the decisions endlessly and surely find "signs" that you could use when evaluating for next time, but guaranteed there will be different forces in play when (not if) it happens again. Don't beat yourself up about it, and don't let anyone else, either.
Hmm, sounds like the logical next step is a dating service to match those traits. Who's doing the cyber-squatting for 23harmony.com and eugenicsmingle.com?
I've never found overclocking to be worth the trouble. Anytime there's a stability issue with an overclocked PC, there's always that nagging doubt that all my troubleshooting is for naught, because it was a fluke bit fail due to the overclocking. Life's too short- skip the anxiety and run your processor at it's rated speed.
So they set up what I imagine is a VOIP setup... all calls through the fiber.
Standard FIOS phone service isn't VOIP, it's POTS signaling over a dedicated wavelength on the fiber- as long as you can keep your ONT alive, you're good to go while the CO is alive. VZ/FTR have tried small deployments of a companion VOIP service for FIOS, but if your phone copper comes directly out of the ONT, it's almost certainly not VOIP. I have an extended battery rigged to my ONT and have kept it up for over a week on battery.
Nice thought, but a majority of the Metro UI has been around since at least 2007 on Windows Media Center/Vista (including the fonts, a proto-version of the tiles, and many other familiar elements).
Compared to the alternatives on Windows, Powershell is extremely powerful, but it does have a pretty steep learning curve. There are a lot of niceties that make me never want to go back to bash or batch (shudder)- killer auto-completion on args (even extends to argument names and values if the right metadata is provided by the cmdlet), verbose and useful error messaging on many things, easy consumption of arbitrary
The interesting part is that a lot of the internal admin tools on newer versions of Windows (and associated server apps like Exchange) are built on top of Powershell, so you can use the UI for basic stuff, then hit the "show me the script" button to get a Powershell script as a starting point for automating something. Similar to the workflow many people used for learning Office scripting ("record macro").
While I've not seen a major penetration of command-line-only scripting for Windows, having *everything* scriptable in a reasonable fashion (and enforcing that by building the UI tools on top of the script engine) is a great way to drive that penetration.
Multi-monitor Remote Desktop (which kicks the hell out of anything else for performance), PPTP/L2TP/SSTP VPN in the box, fast-user switching- what more do you need to make an OS "conducive for telecommuting"? Works fantastically for me...
Except for those that are *part* of the "dying media industry" (think Comcast/NBC Universal and TimeWarner). Same kinds of internal conflict that Sony has for being a provider of devices that can infringe on copyright and a producer of copyrighted content. Guess which side wins (have a look at Sony's crippled devices)?
If it's not already clear, darn tootin' the next version of the volume license agreement will contain the "OnLive" clause that expressly forbids it...
Stop the violator!
"If someone alters your password not through the normal password change process (i.e. an Administrator uses 'reset password'), you lose access to your private keys, and thus your encrypted files."
This is only true for local (eg, non-domain) accounts. Domain account passwords can be changed administratively without affecting the keys.