Be careful with model or even revision numbers, always check hardware compatibility lists. very often times the difference between something like a "653" and a "653+" can be an entirely different (and not supported) chipset.
You do not receive the Google Docs login prompt if your browser is not logged into Google at all.
You do, however, receive the login prompt if your browser is logged in through another Google service (like search). Check to make sure nobody has you logged into Google search or something.
This sort of half logged in status is very annoying.
Yes, but being inspired to write a similar book is now a grey area.
As a some-time composer / musician, I like to play around with existing themes and thus create new themes. Many of history's greatest musical pieces reference other pieces (J.S. Bach referenced traditional church pieces, Mussorgsky referenced many traditional folk songs, the list is probably endless), indeed the vast majority of popular music rarely strays from a handful of progressions around a limited palette of chords. Imagine if someone had managed to patent the 12 bar blues early on... No blues explosion, no Rock & Roll, no Elvis, no Beatles, etc. etc.
The argument that patents are for protecting original ideas is becoming more specious with time. It seems that the primary reason many companies now apply for patents is to either protect themselves from future patent cases, or, as is the case with IV, to prosecute any company or individual who tries to bring a similar idea to market.
I belive there is a real moral hazard to selling addicting/impulsive products, especially to children. After all this is part of the reason why zynga has such a bad reputation.
the issue is, if you have a cluster of games/etc managed by steam in your home directory that is already not under the control of package management, what do you gain by splitting out the steam client itself? it is easier from valve's perspective to just allow steam to manage its own updates along with everything else it manages, than to have a rather arbitrary split that gives you no real advantages anyways.
Steam has always been designed on both osx and windows to be a portable folder that you can move around from system to system and run stuff out of wihout worrying about installers and dependancies.
theoreticly you could work around the library/datafile issues with LD_PRELOAD hacks to make it load stuff from your home directory instead, but thats pretty awful.
path prefixes only generally apply to ./configure scripts when you are generating makefiles.
As paths to libs and stuff are hardcoded as part of the ELF spec, it becomes difficult to implement something like this and ive not seen a package manager that can do it.
Steam has a package so dependancies can be satisfied easily without resorting to "install xyz beforehand", and it runs an installer into your home folder because the user has to be able to modify the games directory for many, many games on steam, because stuff like configuration, custom maps, custom models etc, is stored alongside everything else.
Also steam has diff based patching (which requires accress from whoever is running the steam binary) which makes a lot more sense than how package managers operate for large packages, imagine downloading an entire 20 gig game every time there was a minor bugfix, it would be very obnoxious.
Unless the design of both package managers, and how steam games store settings/etc both change radically, this really is the only workable solution.
Luckily, you will still be able to share steam folders cross user, just simply give both users read/write access to the folder.
"we both recognize that wireless broadband is different from the traditional wireline world, in part because the mobile marketplace is more competitive and changing rapidly. In recognition of the still-nascent nature of the wireless broadband marketplace, under this proposal we would not now apply most of the wireline principles to wireless, except for the transparency requirement. "
IE, nothing about network neutrality, except telling people what you throttle/etc should apply to wireless.
Its best to always remember this, Google was not on the side of "internet freedom" when they recommended to the FCC that wireless networks didn't need net neutrality.
