The Imagination Age

This month’s Tech Review has an editorial that begins “Inventing the future…” and end with these two paragraphs:

“Traditionally, Technology Review hasn’t written that much about society. Our subject matter is emerging technologies, and they have historically been purchased by corporations, universities, and governments. That’s because emerging technologies used to require an extraordinary capital investment, one well beyond the means of most people in their private capacities. Nor did most people see the need to experiment with really novel technologies. Thus the personal computer, the local-area network, the Internet itself were all first used in commercial, government, or academic settings.

”But this is changing. The spread of cheap laptops, handheld devices, affordable Internet access, Wi-Fi, and a dozen other consumer technologies has led to a wonderful explosion of new social applications for them. But here’s the really interesting thing: most of these social technologies have simple editing and programming tools that let ordinary folks do innovative things that risk-averse corporations and government agencies would be hesitant to try. We suspect that Technology Review will be writing about the impact of new technologies on society much more frequently. Besides, social technologies are more fun.”

Here’s the letter to the editors that I just sent:

Continue reading

Un-ironic

The note just below this one, under the heading “The Ironies” juxtaposes mention of my travails due to a broken computer and the horrible tragedy, the horrendous crime, in London today. I did not mean to imply any equivalence between my troubles and those in London, and I meant no insult to the dead, wounded, or to those who love them, or to anyone affected.

Trusting that people of good will will understand that, I’m going to let stand the entry.

And as for you, dear reader, I hope you’ll stay safe today.

The Ironies

For some time now I have been wanting to write that seminal piece explaining the essence of the philosophy of “technoskepticism” that motivated my desire to start up Wetmachine in the first place. My brilliant essay, in the line of the late Neil Postman’s Technopoloy and all of the grouchy, curmudgeonly works of the late, great Christopher Lasch (Culture of Narcissism, Revolt of the Elites, etc) would, in a playful yet dazzlingly serious manner, address the fundamental ironies of our time resultant from the fetishization of technology that has taken on the role of religion in “modern” societies that naively believe they’re past all that.

Perhaps I would address scary (but nevertheless ironic) phenomena like technology-boosted asymmetric warfare as carried out by midieaval fundamentalists — today’s blasts in London presumably the latest sad manifistation thereof. And perhaps I would digress to discuss internet pornography consumption among teenagers in the pro-capitalism Bible Belt of the USA, another region in which the “internal contradictions” of the fundamentalist-technopolist religion play out.

Alas I have no time to work on this essay today. Because I’m really behind the 8-ball at work, as a consequence of having dropped my Powerbook into a puddle of coffee some weeks ago. It’s still “in the shop” and I’ve been reduced to using the virus-infested, 4-year old Gateway(tm) that is our family computer. Let me tell you, this thing is slow. And, I don’t have all my favorite tools installed on it. And there’s nothing quite so frustrating as trying to write a powerful essay on the ironies of technology addiction on a crappy old Windoze machine, that much I’m sure of.

So perhaps some other time.

Black Monday

As I demonstrated last fall when I predicted a Kerry victory, my powers of prognostication are nothing to write home about. OTOH, I suppose this demonstrates the wisdom of the old saw that you ca’t judge an outcome by oral argument.

We lost Brand X by 6-3. Interesting split that put Scalia and Thomas on opposite sides but, as I have observed in the past, telecom issues do not fall into the neat conservative/liberal divisions everyone is so fond of making.

Grokster also went the other way, with the Court not even remanding for trial.

I will have more later when I have read the decisions. Right now I’m trying to sort things out.

Stay tuned . . .

Scaling to the Enterprise (Part 4 of 4)

4. HOW RELIABLE IS THE COMMUNITY?

(See part 1.)

None of the previous matters if the software isn’t useful, or if we are not allowed to use the software. The former is what we’re working on, but the latter is a very complex issue. Croquet is certainly not at critical mass. It could certainly go away. However, we feel it is immune at least from licensing plays such as those that have plagued the use of proprietary systems in higher ed, or those that have fractured the Java community. As the number of users in such systems grows, attempts for controlling proprietary lock-in have been very expensive. Croquet fights this in several ways: with an open source license in which all work on Croquet itself is available to anyone; with a P2P architecture that eliminates any advantage to “controlling the servers”; and with a dynamic language that eliminates any advantage to “controlling the release.” We feel that this last will be further strengthened by upcoming work in architecture and security, to be carried out here at UW. For the general health of the community, I look forward to upcoming announcements.

Je Suis on French TV (Hope I do not sound like une idiot)

O.K., French Canadian TV.
This piece
on a wireless municipal hotspot in Alexandria, VA appeared on Canadian television Sunday night (June 19). As usual, an hour of filming to get 20 second of screen time. I am at the end, rebutting famed ILEC sock puppet David McClure of the US Internet Industry Association.

Sadly je ne parle pas le Francais, so I have relied upon the translation skills of MAP summer intern and Candian native Jennifer Scher, who assures me I do not sound like une idiot. But, really, what else is she going to say.

Stay le tuned . . .

Scaling to the Enterprise (Part 3 of 4)

3. HOW WILL APPLICATIONS BE DEVELOPED?
(See part 1.)

It is not practical to expect users to develop applications in Squeak. There is too much to learn. But neither is it practical to expect users to develop applications in Java or ANY OTHER COMPUTER LANGUAGE. There is no way that any community of professional developers could possibly keep up with the demand that we hope for unique applications. No matter what language they used, nor even how many developers were available. There’s simply many more users — and user needs — than there are developers. As with scalability of load, we need another approach. The answer is the same: push the load to the edge of the network.

Continue reading

Scaling to the Enterprise (Part 2 of 4)

2. HOW MUCH USE CAN THE APPLICATION SUPPORT?
(See part 1.)

The architecture of Croquet is very different from that of, for example, J2EE applications. In a client-server application, one server or server “farm” must process each and every interaction initiated by the thousands or millions of users. The only thing processed on the end-user’s computer may be as little as the HTML formatting of the text and image results. Every single other computation must be handled on the big-iron servers. To double the number of users, the capacity of the servers must be doubled. It should be no surprise, then, that so much effort goes into trying to squeeze out each available computing cycle in such architectures.

When an application has state — that is, when results depend on previous results rather than simply generating static files — client-server does MUCH worse. The amount of storage required can go up much faster. In some cases the application state depends on the number of possible connections between users or between applications. The storage (and certain kinds of search-like operations) increases as the square of the number of users or applications (N^2, c.f. Metcalfe’s law). But we are particularly interested in allowing students and faculty to form their own ad-hoc groups among which to communicate and solve problems. A client-server architecture hosting such “group forming” applications would grow exponentially to the number of users (2^N, c.f. Reed’s 3rd law). With only a few users, this architecture would not work at all, no matter how (finitely) fast the servers, or what language the application is written in. (See Reed’s discussion for a surprisingly accessible treatment of value, saturation, and other issues.)

Continue reading

Scaling to the Enterprise (Part 1 of 4)

Croquet is built on some well-used, but not mainstream technologies. A colleague has asked “Why should we believe that Squeak scales to the enterprise?” I’d like to share my answer, to solicit comment.

It is good to ask this, and there are several aspects to the answer:
1. How reliable is the underlying software?
2. How much use can the software support?
3. How will applications be developed?
4. How reliable is the community.

Part 1 of 4.

Continue reading