You might want to learn the difference between its and it's
I know the difference, but how should I go about teaching this difference to the virtual keyboard of a mobile device? Or is there a key ACM paper on how to guess where "its" or "it's" should go in context?
The Xposed framework
Xposed requires root. Why do so many more GNU/Linux devices than Android devices come with root? And how do I get a headphone jack fixed after I have voided the warranty by having installed a rooted ROM?
Using software in wine is not really looking beyond Microsoft.
By that standard, using software in GNU/Linux is not really looking beyond Novell because just as Wine is a free reimplementation of Windows API, GNU/Linux is a free reimplementation of UNIX.
Research, buy, take responsibility.
How should I "research" thoroughly if the product isn't even available for inspection in my geographic area?
nobody uses physical media anymore
"Nobody" is a strong word. People who pay $10 per GB for home Internet (sat, cell, or Iowa DSL) still use physical media.
there's zero reason not to stick the PC somewhere else and run an extra CAT-6 drop
Unless you're renting and the landlord won't let you modify the walls.
I don't like seeking after misery, so I avoided opening a Comcast account to begin with. They may own almost all the market, but there are still less obnoxious alternatives.
For you, did such avoidance involve finding a different city in which to work? Or did it involve dealing with sat or cell ISPs that charge $10 per GB?
"Fair use" does not actually make copying legal. Rather, it's a defense to the accusation of copyright infringement.
How so? I was under the impression that a defense to infringement makes certain forms of copying legal because it's a defense.
You still infringed the copyright
Then I must have misread the phrase "...is not an infringement of copyright" in 17 USC 107. What was it intended to mean?
Who the hell buys/uses CD's anymore?
People who are fans of recording artists who choose not to sell their music on Amazon MP3. For example, AC/DC and Garth Brooks are noted for their opposition to sales of downloadable singles. Other artists like the Beatles are exclusive to iTunes, which is fine if you use OS X or iOS but leaves, say, Android users behind.
[Online games and offline apps] are mutually exclusive.
True. Should I have instead split the two scenarios into separate comments?
An offline application can't know that validation has changed or there is an app update because it's offline. At that point, what do you do, toss out any data the user entered while they were offline?
In the case of an application with a substantial offline component, the server would handle the current version of the client and at least one previous version.
Even if I follow your approach, when the client and server versions mismatch because the user was offline they'll get the same pages of errors.
Granted, the user may see a few errors when server version n communicates with client n - 1, mostly related to the (hopefully small) schema changes between n - 1 and n. But ideally, this should introduce far fewer errors than if there had been no client-side pre-validation at all.
Boy, I hope your QA team has a large alcohol budget and the world's largest whiteboard for their validation testing matrix.
It's a bit easier when the testing matrix is a band matrix. If X is the client version and Y the server, the server only needs to gracefully handle a small number of client versions.
But now your client's validation doesn't match, unless you're going to go around and force all your clients to update. Maybe at gunpoint or something. Who knows.
Online games won't play unless at the latest patch level, for example.
if you need to do complicated validation why the heck are you doing it on the client? Just send it to the server
Because the user is using the application during a 2-hour period of having no access to the Internet.
and then let the server return an error
So your suggested workflow is just to let the user enter grossly invalid data for two hours then have the server present pages of error messages once a connection is reestablished.
Hence the growth of Node.
I don't usually see server architectures and client architectures sharing too much in the way of logic code
Input validation logic and any logic related to offline use needs to be the same (or at least provably identically behaving) on server and client.