airborne wind turbine

This is such a good idea! Even better, it could have two counterrotating turbines, either in series (coaxial) or in parallel (twin air channels), to reduce issues associated with torque.

Bookmarks Bar folder labels, brevity, and OS naming

I don't, but if I did have a Bookmarks Bar folder for Android, it would probably be labeled "Andrd" for the sake of brevity. Brevity is at a premium because I have a lot of Bookmarks Bar folders, and like for them all to be visible when I'm browsing. I do have a folder for non-Apple websites that focus on Apple and its products, and that folder is named "iOSX". If I weren't so concerned with keeping it short and more concerned with precision in folder labels, I might rename it i/OS/X, to indicate that there's a spectrum of devices running a spectrum of operating systems, all closely related.

What primarily distinguishes iOS from OS X is the user interface paradigm supported, touch screens versus mouse/trackpad and keyboard. But this quickly becomes a less clear distinction when you consider that iOS devices already support keyboards, both virtual and physical, and might at any time gain support for pointing devices, and Mac trackpads already support gestures, even if they're not identical to iOS gestures.

At some point in the not-to-distant future, maintaining the distinction between OS X and iOS may no longer make sense, but by that I don't mean the obsolescence of keyboards and mice, rather I mean support for whatever user interface equipment is available, be it touch screen, trackpad, mouse, keyboard, eye tracker, stereo video for mid-air gestures, or voice, with an API that makes basic functionality available regardless of the user interaction mode, while offering the opportunity to tweak performance in particular modes.

This is far easier to say than to do, but there's some evidence to suggest that Apple has been hard at work making it possible.

A secondary distinction between iOS and OS X relates to the sandboxing of apps. In iOS, third-party apps on non-jailbroken devices have been sandboxed from the get-go, whereas on the Mac sandboxing is a recent thing, and only necessary for apps distributed through Apple's App Store. For that matter, kernel extensions are still allowed in OS X, and will continue to be allowed on a limited basis in Mountain Lion. But the issue isn't really about sandboxing versus developer latitude; it's about security and utility, two goals which aren't necessarily at odds.

When Apple finds a way to bring the utility of OS X to iOS, without sacrificing security, and to bring the security of iOS to OS X, without sacrificing utility, it will be time to discard the distinction, and perhaps rebrand the recombined system "iOSX".

Proview like a crooked used car dealer

Here's Apple's statement regarding Proview's claim that it never licensed the name "iPad" to Apple for use in China

“We bought Proview’s worldwide rights to the iPad trademark in 10 different countries several years ago. Proview refuses to honor their agreement with Apple, and a Hong Kong court has sided with Apple in this matter.”

What Proview has done is very much like a used car dealer who sells you a car and then later claims that the engine wasn't included in the deal, sues you for damages because you're using the engine, and calls the police to stop you from driving the car until you pay, explaining that the agent who sold you the car didn't have the right to sell the engine with it.

I wonder what the government of the PRC would do in such a case.

Siri and Apple's long history of anticipating voice/touch/agent user interfaces

The USPTO has just published the first heavyweight Siri-related Apple patent application, and Patently Apple makes it almost comprehensible. Of particular interest in that article, is this speculative Apple-created video from 1987…

deep truth from an irreverent crew

This link leads to the last few minutes of the 13th and final episode of what should probably, on the whole, be called a mockumentary, based on a group visit to North Korea.

progress, and the factors which constrain it

While the timing of the transition from one year to the next is arbitrary, an artifact of the choices made in calendar design, the passing of time is at least a persistent illusion, and the metamorphosis which accompanies it convincing. "The times, they are a-changin'", as a younger version of Bob Dylan once sang. Change has been a frequently recurring factor in the lives of myself and my contemporaries, like a stressed and agitated Earth repeatedly shifting beneath our feet, and much of it at least seemingly not for the better.

I say "at least seemingly" because for any change there will be cascading effects which are difficult to predict at the time, and these cascading effects often interact in surprising ways, so even if you find it hard to believe in "progress" you can still place hope in serendipity.

Having a basic education in biology, the way I see progress is informed by the simple rule of thumb about plant nutrition I once learned, that the growth of a plant is constrained by whatever nutrient is least available (relative to the proportions in which all nutrients are needed). Similarly, progress depends on all of the necessary conditions being in place, or at least acquirable, not just one or two of them, and resources spent on bringing the limiting factor(s) up to snuff yield the most bang for the buck.

So what is/are the limiting factor(s) hindering progress? I can think of a few.

One has been the cost of computation, but it could scarcely be called a limiting factor anymore, even though many applications remain for which the necessary processing capacity continues to be prohibitively expensive, and/or too power hungry. Much that hasn't yet been done could be done within the limits of current technology.

Another is the knowledge and experience to make good use of that computational power. This too is changing, but it's trailing behind the improvement in computing hardware. I'm referring here not only to software but to techniques for interfacing with the physical world, the sensors and actuators of robotics, and the integration of all these into working systems.

Less obviously, but perhaps more importantly, progress has been constrained by what we have (habitually) used these improving technologies to do. To riff on the old saying about when you have a hammer everything looks like a nail, we have, until quite recently, treated every new thing to come along as another kind of hammer, and measured its value in terms of how good it was at driving nails. In other words, we haven't been much interested in changing what we do, only the details of how we do it. I believe people are generally ready to climb out of this rut, if they could rely upon mutual support in doing so.

Progress has also been limited by how we organize ourselves, primarily driven by the conservatively defined interests of capital. There's been a great deal of experimentation with alternative ways of bringing people together to do creative/productive work collaboratively, much of it supported by venture capitalists, but there's still a lot of inertia in the old way of doing things and not yet enough successful counter-examples to point to, or enough general experience with participating in them.

And finally, there is a tremendous need for remedial education in science, technology, engineering, and mathematics, most of which will have to be conducted remotely, via self-instructional packages, video courses, or mass media. I believe this deficit to be the twin product of the counterculture's rebellion against all things technical and a resurgence of the thread of anti-intellectualism that runs through western culture, which can perhaps be traced to Celtic pride in the lack of a written language, but which in any case has been encouraged by those who find a well-informed, clear-thinking populace inconvenient.

Most of us are in a position to work on one or another of these, even if for now it's only to educate ourselves. Let's get to it!

reforming agriculture through more sophisticated mechanization

Historically, at least since the mechanization of agriculture began in earnest, there have been two primary measures of agricultural productivity, the amount that could be grown on a given acreage and the percentage of the population required to feed all of us. The former, measured in bushels or tons per acre, has generally been increasing and the latter, measured in man-hours per bushel or ton, decreasing for at least the last hundred years, albeit more so for some crops than for others. (A consequence of the decreasing need for labor to produce many staples has been the migration of the children of farmers to cities, where they helped keep the cost of labor low in other enterprises.)

Corn (maize) is a good example of a crop for which these conventional measures of productivity tell a story of brilliant progress, with the result that corn is cheap enough to use not only as livestock feed, to be converted into meat and dairy products, but as the feedstock for production of ethanol for fuel, competing with fuels refined from petroleum pumped from the ground, rather remarkable considering that corn kernels represent only a small fraction of the biomass of a corn plant and that fermentation and distillation aren't particularly efficient processes.

Crops that fair less well by these measures include many vegetables and most fruits, which have been becoming gradually more expensive, especially as compared with grains that are easily handled mechanically, but even compared with meat and dairy products from grain-fed livestock. One major consequence of this has been that people generally consume more grains, meat, and dairy products, and less fruit and vegetables than they once did, before the mechanization juggernaut got started and while vegetable gardens were still common.

So, by an altogether different measure, how healthy the average diet is, mechanization has been a disaster, so far. I say "so far" because the essential problem is that, so far, mechanization has favored crops consisting of hard, dry seeds, that are easily handled in bulk, making other crops needed for a balanced diet relatively less affordable. In happier economic times this would matter less, as people would simply pay the premium for a healthier diet, but the times being what they are people are scrimping however they can, including with the food they consume.

There are other ways of measuring productivity: energy use*, soil gain or loss*, water use and contamination*, and the degree to which a given practice denies space to native flora and habitat to native fauna. By any of these measures, conventional mechanization comes out looking at least shortsighted if not dimwitted.

*(per unit produced)

So is the answer to turn back the clock on agricultural technology, to replace the plow with the hoe and the drill with the planting stick? I'm not prepared to make that argument - although I've no doubt others would - aside from noting that gardens are a better use of many urban spaces than are lawns, and there is no further need for rural communities to supply cities with cheap labor, since those cities are already well supplied, and many rural areas suffer from depopulation.

Instead, my position is that we need to take mechanization to the next level, replacing dumb machines suited only to bulk operations with smart machines capable of performing well-informed, detailed manipulations, for example controlling weeds by selectively pulling them from the ground or pest caterpillars by picking them from plants (unless they've already been parasitized, as by wasps) rather than by applying poisons.

Given machinery with an adequate array of sensors and a sufficiently broad range of optional actions, applying best practices becomes a matter of mating these with processing power connected to an expert system, and of programming.

It gets better, because the same system that works the land can be used to improve the expert system through experimentation and, in routine operation, by accumulation of data to which statistical methods can be applied, and can also be used to improve the crops themselves, as for instance by leaving the best formed, most insect resistant cabbages to go to seed.

The bottom line is that this approach can make available the mechanical equivalent of an attentive expert gardener, at a cost, given predictable economies of scale, that would make possible the wholesale replacement of conventional, traction-based machinery and methods with more adaptable machinery bringing a whole new repertoire of methods to bear, one far better suited to the production of the fruits and vegetables that have been becoming unaffordable under the current regime.

As for the other measures of productivity mentioned above, such machinery, since it wouldn't need to turn soil in bulk and could operate long hours without continuous supervision, would consume energy at a relatively low rate, suitable for supply from solar panels or via the grid from renewable sources. It could operate through continuous ground cover, all but eliminating soil loss, and with minimal use or complete non-use of herbicides and pesticides, reducing soil and water contamination. Ground cover, mulch, and the humus accumulating from decaying roots can also reduce the need for irrigation, and the ability to create local varieties through seed selection based on the health of maturing plants can further reduce it, as well as helping to adapt more quickly to climate change. Making room for native species, something that can only be accomplished in conventional practice by leaving land completely undisturbed, becomes a matter of programming the system to leave certain species alone, wherever it finds them, even to the extent of tolerating some crop loss to native fauna, and to leave anything it can't identify alone until it can be identified.

Such machinery might not be able to compete with conventional practice in the production of corn and other bulk commodities, at least to start with, but it also wouldn't consume prodigious amounts of petroleum-based fuels. Moreover, development and rapid deployment of such machinery would drive the growth of a new, potentially domestic industry, one that would also work to the benefit of materials recycling efforts, more efficient transportation, and on and on.

The R-word I haven't yet mentioned is robotics. While such machines probably aren't what most people first think of when robots are mentioned, their creation and production falls squarely within the discipline of robotics, composed as they would necessarily be from robotic technologies.

monitoring fields with UAVs

They're using radio-controlled aircraft rather than autonomous machines, but it's still a big improvement over the time spent walking fields or the lack of detail that comes from only checking the edges of a field. I expect further improvements with the introduction of better sensors and on-board controllers.

The Rambunctious Garden: Emma Marris

Go check out this post about Emma Marris's Rambunctious Garden on my Cultibotics blog.

Microsplat: How Microsoft's business could collapse

Business Insider has published an article, STEVE BALLMER'S NIGHTMARE: How Microsoft's Business Actually Could Collapse, outlining several mechanisms which could coincide to cause Microsoft's revenue stream to contract dramatically, likely Microsoft responses to these pressures, and alternative takes on the outcome.