My preferred method is "the heat death of the universe".

Plus how much per month? AT&T forces "smartphone" users to buy a data plan.

The problem with using a Windows Phone is that AT&T will probably still make you pay for a data plan that you don't use.

You really do *not* want the honest answer to this question, but I will give it to you anyway: So people who would otherwise be employed asking "Would you like fries with that?" can get non-performance critical programming jobs.

You *always* have to be closer to the hardware:

#1: Almost everything is a mobile device these days; people buy laptops instead of desktops, cell phones music players, etc.. The closer you are to the hardware, the better your battery life, the lower power your processor can be to do the same amount of work, the cheaper the unit price for the lower powered hardware and smaller battery, the lower the cooling system costs (mostly, you can go without them, or operate them on "low"), etc., etc..

#2: Being closer to the hardware lets you reduce the number of blades/servers/PaaS instances that you require in your data center or cloud. This reduces costs, again in terms of cooling, but also in rack space, and power requirements. Facebook rewrote their PHP code to be compiled to binary code, and it saved them over 50% in servers. When you are a startup, and have tons of VC money to throw hardware at a problem, you can get away with not having to worry about those things, but when it's time to get to scale, they start to become major issues.

You can *get away* with not being closer to the hardware... for a *short time*, when you are engaged in rapid churn (e.g. new web UI ever 2 hours), or doing a lot of rewrites or running on hardware that better than the hardware you intend to deploy on, but after that being closer to the hardware is *the overriding thing*.

Answer to the related question... "What smart phones out now are (or can be reasonably outfitted to be) closest to a dumb phone, considering reliability, simplicity, and battery life?".

That's easy: any of them that you don't install all of those crappy, battery-sucking Apps on, and turn off polling for push notifications from Facebook, email, and so on, so they they aren't constantly running the battery down because then they can actually get the application processor into sleep state once in a while without some stupid polling interval waking them up to use more battery every few picoseconds.

AT&T 210M Trimline; no battery needed, it gets it's power from your landline so it works in a power outage, never has reception issues.

Hey, if you are going to be retro-technology boy for no good reason, might as well plug your phone into the wall while you are at it.

A Chromium build that has full feature parity with Google Chrome might have to wait another decade until certain MPEG patents expire.

Then let me rephrase: What's the right tool for entering both native language text and program code?

So the first steps are to 1. learn to find friends, and 2. learn more specifically to find friends who use torrents. Could you elaborate?

We do have a widely adopted Lisp. But it's not Java; it's JavaScript. JavaScript implements Lisp-like semantics, and its syntax is a C-colored fulfillment of the "M-expression" syntax concept originally envisioned for Lisp.

Only because Oracle keeps breaking it. The Java virtual machine's security has proven to be Swiss-cheese enough that Oracle is falling back on the traditional video game console security paradigm (reliance on commercial code signing certificate authorities) rather than actually restricting what a program module can do.

Which isn't necessarily good style.

First, the type name in a declaration can and often should be more generic than the constructor. It could be an interface that the constructed class implements or an abstract class that the constructed class extends. For example, you can do Map map = new TreeMap() if you're not going to call any tree-specific methods later on.

Second, why name the variable similarly to the class? Map enemies = new TreeMap() makes the variable's purpose easier to understand.

The amicus brief by Dr. Seuss Enterprises in Eldred v. Ashcroft implied that one key objective of a long copyright term is to cover adaptations into new mediums created decades after first publication of a work.

Reading from standard input does not mean "reading from the command line". Standard input is often redirected from a file, from another program's output (called a "pipe"), or from data provided by the client that connected to a running server.

Rapidly switching back and forth between en-US and the keyboard layout for your native language can be uncomfortable as well. "Doctor, the contortions that I have to make between doing this with my arm and doing that with my arm hurt. I am required to do both for my job."