I gather many of them are people at work who lack privileges to install other browsers or to run executables from writable directories. This is reportedly common on government PCs that need to connect to IE-only intranet apps.

CDMA2000 is the cellular technology stack used by Verizon and Sprint, which traditionally (as implemented in the United States) does not use a removable CSIM card.

Sounds sort of like NoScript. Under your proposal, who would manage updates to scripts that have been approved? If you instead want browsers to require the user to download scripts first, what user interface would you have browsers provide for that? Because a browser could just display "Please load scripts" or "Please update scripts" on a white screen until the user does so.

SIM-only plans work where T-Mobile has good coverage. But in the states, not all carriers use GSM. If you happen to be located in an area where only a CDMA2000 carrier like Verizon has a good signal, a SIM-only plan won't work because CDMA2000 carriers in the USA have tended not to use CSIMs.

The games are either A. dumped using a Retrode adapter or B. pirated.

The rules change for each other system with which your system has to integrate.

That'd be something consider. Amazon, for comparison, had to make its own updater for Amazon Appstore.

All supported Windows desktop operating systems can run IE 9 or later. Besides, whether and why government employees on government equipment and government time would be watching your video still depends on what the video is of. It might be better in a specific case to download the video to watch in a native, non-web application, or to have the IT department authorize installation of a second browser for "general interest" web sites.

Perhaps the disagreement is whether it counts as "version control" to have a weekly tarball as the revision history and diffs as the change sets.

Then how does one "create something fun with simple tools" and still eat? Besides, even if you have an unrelated day job, how does one "create something fun with simple tools" if the tools have to interoperate with other tools that are made available only to established companies, as in the case of developing games and other applications that run on devices commonly connected to TVs?

Only in your first couple projects. By your third DOS project, you probably would have built up your own UI library.

But the big thing that DOS did better than Windows back in the early to mid 1990s was using all the features of the VGA. DOS applications could run in low definition (Mode 13h, Mode Y, and Mode X, with resolution of 320x200 to 320x240). This allowed updating the whole screen before Windows finished updating half of a 640x480 standard-definition screen. DOS could also use hardware scrolling to pan over a large virtual area without having to do the bit shifting bullcrap that plagued standard VGA mode back then. Both of these became less relevant, however, as CPU speeds and bus speeds rose and especially as graphics cards began to incorporate 3D rasterizers.

The problem here is that once "a program or a script" reaches some level of generality, configuring it becomes almost as hard as just creating the links yourself. Hence the reference to application programming interfaces (APIs) and domain-specific languages (DSLs) in the article.

And watch suppliers decline to do business with your startup company because they don't like your lack of experience or they don't like where its office is located. For example, some makers of computing platforms lock down who's allowed to have a devkit, and they have a history of reserving devkits for the most experienced companies with traditional offices.

In some North American markets, especially those served by CDMA2000 carriers, it's either buy your phone from the carrier or get 0 bars. These carriers tend not to sell any devices that allow viewing web pages and loading user-made apps without Apple's walled garden or Google's alleged spyware. Is your "simple fix" doing without?

The difference between iOS and Android in this respect was that during the Android 1.x days, manufacturers and carriers sold Android phones in countries where Google hadn't yet opened Google Checkout. This meant that in order to get an app into Android Market in any of those countries, the developer had to make the app available without charge. The common way to do that involved selling advertising space. This set price expectations on Android lower than they are on iOS, where Apple has made sure to open the iTunes Store in a country before selling iPod, iPhone, or iPad products there.