In some ways it's still 1984, especially for mobile dev: > Highly optimizing compilers aren't worth the risk. Rewrite slightly to "non-mainstream toolchains a

In some ways it's still 1984, especially for mobile dev: > Highly optimizing compilers aren't worth the risk. Rewrite slightly to "non-mainstream toolchains aren't worth the risk". Should you write your next game in pure Java, or use JNI/C++, or use Unity, or something more obscure? No matter which you pick, you'll be running to StackOverflow (if you're lucky) to fix the periodic show-stopper. Using the most popular tool gives you the highest likelihood of success without delving into library source code. > Something is wrong if most programs don't run instantaneously. Forget startup time -- Make a 1980s developer deal with iOS code-signing issues and watch them switch their occupation to animal husbandry. > Everything is so complex that you need to isolate yourself Back then documentation was delivered in thick paper volumes which often contained more bits of information than the software being documented. Now we just Google StackOverflow and cross our fingers.