Friday, November 05, 2010

getting a handle on Flash

Cult of Mac has published instructions for uninstalling Flash, together with instructions for reinstalling it if you decide that's what you want, and a pointer to ClickToFlash, which replaces Flash content with an inert rectangle bearing the word "Flash", unless you click on that rectangle, in which case the Flash content is displayed.

And here's John Gruber of Daring Fireball on essentially the same topic.

Friday, October 29, 2010

code as content; code as a vector of change

First came symbolic speech. Thousands of languages and dialects blossomed, and the words of some, the shamans, those believed to have direct experience of a spirit world, seemed to possess magical potential.

Then came writing. The great variety of spoken language began to be replaced by preservation approaching permanence, joined shortly by the rigor of peer review and explicit criticism, and the magical potential of the words of the shamans, became invested instead in interpreters, the priests and scribes.

Perhaps presaging what was to follow, a variant of writing, plays, developed into instructions to be performed by acting companies.

Then came machine code, a variant of writing that controls the operation of hardware designed to process such instructions. Very early on that machine code gained conditional branching, the ability to perform different sets of instructions based on the value of some numerical/logical expression. At that point it must have already been apparent to a few that something like machine code would eventually surpass conventional writing, by virtue of its potential to directly control the actions performed by machines. At about the same time, a process of increasing abstraction began, whereby machine code was wrapped in assembler code, which was itself wrapped in higher languages, more closely resembling conventional writing.

Thus far, the impact of computer code on what these days passes for natural language (speech having already been molded by thousands of years of close association with writing) has been to facilitate its production, dissemination, and consumption, but that's only a small part of the whole story.

Computer code, embedded in machinery, has the potential to render meaning tangibly, as real physical performance, with real consequences, good or bad. Given that the design and production of machinery is itself becoming increasingly automated, the question becomes one of what you want the machines to do, and not do, and how those desires can be represented in code.

For example, I can say that I want to preserve what remains of Earth's original biological diversity, while at the same time reducing the dependence of agriculture on petroleum, but in that form it is merely a feeble wish, displaced by the next thought. I can write a treatise explaining why we ought to do what we can to preserve what remains of Earth's original biological diversity and free agriculture from dependence on petroleum, and it may stir others momentarily, but it takes more than that to make any real difference, and if I were to be asked exactly what I'm talking about in practical terms my answer isn't likely to satisfy those whose livelihoods would be effected by any such initiative.

If, on the other hand, I express my intention in the language of machine design and control logic (computer code), the implications, not only of the basic design but of various approaches to managing the system, can be explored through simulation, and that expression goes a long way towards constituting a detailed plan for its own implementation. It's all just code, even the design for the physical machinery, but in a form that makes the decision to go forward with it almost as easy as the decision to flip a switch, at least as compared with a vague call for the desired end results.

Such a project would be too big for any individual, of course, so tools that facilitate collaboration on such projects are needed. Some such tools already exist; others remain to be invented, and much effort is being expended in this direction, even if those involved don't see their work in such grand terms, with the potential to achieve change that could never be achieved through conventional political means alone.

Thursday, October 21, 2010

the parts of Lion which remain secret

I must confess some disappointment over yesterday's announcement, not because the stuff they showed wasn't cool - it was! - but because the stuff that interests me the most remains secret. What we saw of Lion were mainly user interface enhancements, a category that was famously, intentionally missing from Snow Leopard, which concentrated on bug fixes and lower level enhancements. It might even be that the pause in the introduction of new user interface features, represented by Snow Leopard, made possible the integration of such features seen in Lion's new Mission Control view.

But what's Lion got to compare with OpenCL and Grand Central Dispatch? Something, most likely, but that something remains secret. Does it have a new file system or file system abstraction layer? Does it bring true resolution independence? Are any technologies developed for Apple application software, like iPhoto's face recognition, moving into system code and becoming available to third party applications? Are there any important new APIs?

Patience, I try to tell myself, which of the major releases of Mac OS X has not brought such advancements? Maybe 10.1, which was primarily a bug fix and code efficiency update to 10.0. Are they out of ideas? Surely not! Are they underfunding lower level R&D? Not likely. What then?

A Mac OS X engineering position announcement awhile back stated quite plainly that a successful applicant could wind up working on something unprecedented and revolutionary. Sure, Apple spreads such verbiage a little thick at times, but the clear implication was there's something big happening in the wings, and the timing was such that it's likely to be included in Lion, which won't be released until next summer.

Moreover, in yesterday's collection of announcements, everyone on stage was careful to point out that only some of Lion's features were being shown. Clearly there's something else, something they aren't yet ready to talk about.

Something else Steve was careful about, in discussing touch input on Macs and how they've concluded that it just doesn't work on a vertical screen, was that he was talking about laptops, not necessarily all Macs. So, perhaps this recently revealed Apple patent is more than a design exercise. Time will tell.

Wednesday, October 13, 2010

Nice kitty!

The invitation for an Apple Event taking place one week from today strongly suggests that the primary topic of the day will be the next major version of Mac OS X, 10.7, and that the cat-name for this version will be "Lion". Cheetah, Puma, Jaguar (the first to be marketed as such), Panther, Tiger, Leopard, Snow Leopard, and now Lion.

Recent versions have brought, in no particular order, the Kernel Extension APIs, the Acceleration Framework, Spotlight, Core Animation, Core Data, OpenCL, Grand Central Dispatch, and Objective-C 2. What might 10.7 have in store to match these?

Something, no doubt. ;-)

Friday, September 17, 2010

China meets the iPad

China isn't just another market, much as the iPad isn't just another gadget.

China is the most populous country on Earth and has one of the fastest growing economies. So much for the obvious.

While China's economy is rocketing upwards at an annual rate of eight percent, the spending power of most individual citizens is still modest, which makes the affordable iPad a good match.

What makes it an even better match is the touchscreen input, which doesn't discriminate against character-based input, providing the iPad an even greater advantage over keyboard-based netbooks in China than elsewhere.

The advantage the iPad has over other touchscreen tablets, running other operating systems, is more subtle but still substantial, deriving from factors such as attention to detail in both hardware and software, a fast-maturing application software market, and the goodwill Apple has gained through its efforts to improve conditions for the hundreds of thousands of Chinese workers involved in manufacturing its products (even though it turns out those conditions weren't so bad in the first place, aside from the economic incentives for workers to put in exorbitant amounts of overtime, or to end their lives for the compensation their families would receive as a result).

The iPad is destined to be a particularly huge hit in China, but the whole world will benefit from this.

Tuesday, August 31, 2010

AutoCAD returns to the Mac, and comes to iOS in the bargain

As before, I merely pass along a pointer to Architosh's report, which discusses the iOS companion program as well as AutoCAD itself.

Architosh also reports on what appears to be a 60-second TV spot, produced (or at least paid for) by AutoDesk, the company behind AutoCAD.

Monday, August 30, 2010

perseverance and pride

I've already said most of what there is to say about the event itself here, but what I only mentioned briefly there is that it's been a long, long time coming, with the project going through metamorphosis again and again. I had a need to do something that would contribute to bringing the world of music back around to an appreciation of the role of harmonics in melody, not just in harmony, or at least that's how it began. Arguably, I've accomplished that.

Along the way it also became an issue of pride in craftsmanship, as an amateur programmer with experience in Apple's approach to supporting application software. That and avarice may collaborate to drive the project further, perhaps much further, but for now I have a sense of contingent satisfaction, the degree of satisfaction being contingent on the degree of traction my creation manages to garner.

Of course, a free app with no ad revenue doesn't do much to feed avarice, so I'm left with pride in craftsmanship, for now, which is probably just as well; it's what drives me to do my best work.

Thursday, August 26, 2010

party politics in a nutshell

I'm registered to vote, but not affiliated with any political party, at the moment.

That said, here's what remains of my impressions of the two main political parties.

The Democrats have a huge investment in appearing high-minded, and consequently manage to be right about what should happen a little more often.

The Republicans have two distinct constituencies, for one of which they must appear to be at least adequately morally upright, and for the other of which they must make it clear that morality doesn't extend to the wholesale confiscation and repurposing of wealth. It's a delicate dance, and, as a consequence, they manage to be right about what will happen a little more often.

Both are people, with all that means, good and bad.

Tuesday, August 17, 2010

how to improve upon Mac OS X 10.6?

Update: John Siracusa weighs in

From my perspective, that looks like a tall order, but so far it's looking like a slow news week, and Cristopher Ryan, writing in the Apple Blog, has asked What Could Make OS X 10.7 Great? so I'll have a go.

Without really understanding the issues involved, let me echo Ryan's call for a new file system. Everyone who followed such developments seemed encouraged by the hope that ZFS was just around the corner, when it appeared to be so, and then Oracle bought Sun Microsystems and suddenly we were back in bed with HFS+, with no realistic alternatives on the horizon. Meanwhile, whatever Apple is using for a file system in iOS devices is fairly free to evolve, since iOS apps are sandboxed and only have access to the narrow slice of that system that relates directly to them. Also, being flash memory devices with no hard drives, they have different abilities and requirements as compared with a desktop machine. One possibility for the future is that iOS's refined handling of flash memory might be grafted into HFS+ at about the same time that Macs other than the MacBook Air get a bank of flash memory or a solid state drive to augment their massive (but slower) hard drives. Granted, this probably won't be enough to satisfy those who really understand file system issues.

Another iOS capability that might be brought to Mac OS X is the full-blown touch interface, not just the trackpad gestures supported by the Magic Trackpad (which I love!). (If you think the possibility of touchscreen Macs isn't even on Apple's radar, check out this and this.)

Something not yet implemented in iOS, that I hope to see sooner rather than later is low-level support for machine vision, stereo machine vision to be precise, meaning dual video cameras atop MacBook screens and Cinema Displays, or, perhaps better, a dual camera accessory, also sporting stereo microphones, with motorized pan, tilt, and zoom, as well as automatic focus and aperture, benefitting from the same attention to detail as the original iSight. It would be enough if it could do good quality stereo video recording, editable in iMovie, to begin with, leaving any machine vision applications for the following year.

Mostly, I'd like Apple to continue with the transformative process that was the main selling point of 10.6 over 10.5, making the next version even more coherent, robust, and svelte.

Sunday, August 08, 2010

whichever comes first

An Engadget article on the relationship between Apple and AT&T cites a legal action as confirming "the handset was originally locked to AT&T / Cingular for a full five years." In reading that it occurred to me that there might have been another factor written into the original contract, some number of iPhone activations, that would automatically shorten the period of exclusivity if it were to be reached before the full term expired, without any renegotiation of the contract.

Given that iPhones have out-sold everyone's expectations, such a clause could be expected to fire, but the exact timing would remain indefinite until just a few days remained.