Category Archives: software

the ethics of web applications

Eddie Tejeda, a talented web developer based here in Brooklyn who has been working with us of late, has a thought-provoking post on the need for a new software licensing paradigm for web-based applications:

When open source licenses were developed, we thought of software as something that processed local and isolated data, or sometimes data in a limited network. The ability to access or process that data depended on the ability to have the software installed on your machine.

Now more and more software is moving from local machines to the web, and with it an ever-increasing stockpile of our personal data and intellectual property (think webmail, free blog hosting like Blogger, MySpace and other social networking sites, and media-sharing sites like Flickr or YouTube). The question becomes: if software is no longer a tool that you install but rather a place to which you upload yourself, how is your self going to be protected? What should be the rules of this game?

speed dating sophie

Last Tuesday I was formally introduced to Sophie. Our first date left me dazed and confused. She is a powerful multimedia application from New York, well funded and growing under healthy cosmopolitan influences, while I am a digitally challenged graduate student with a dreadful Third World education. Despite the obvious mismatch, Sophie was surprisingly responsive. For a program that is still a month away from even entering beta purgatory, to freeze up once in a while is perfectly normal. My reaction, on the other hand, was childish and immature. I protested out loud, argued with developers, worried about details, and became permanently infatuated. Now I can’t stop thinking about Sophie.
The problem is that she lies at the core of everything I want to do. During the next couple of decades I would like to participate in the collaborative development of multimedia ecosystems. Ok, that sounds awfully pretentious. What I really want is to work and play with a bunch of friends in a huge toy factory. My favorite toys are multimedia creatures.
For a while (and halfway-tongue-in-cheek) I have been training myself to think about all kinds of cultural artifacts in evolutionary terms. When I play around with a good old printed book, for example, I try to think about it as a potentially feature-rich creature that, so far as I am concerned, is working very well in frozen text mode. All other noisier and flashier possible forms of behavior have been muted, so to speak, in order to maximize the cultural value of the reading experience.
I think Sophie fascinates me precisely because her future depends so much on achieving a creative balance between simplicity and complexity. If everything goes well, Sophie will be able to handle very intricate tasks in rather plain terms. The program already has an unobtrusive but intuitive interface that would allow first time users to assemble rich multimedia documents in a matter of minutes. A highly sophisticated Sophie document can be embedded as a whole into another Sophie document. Placing an entire library of interconnected multimedia artifacts in a corner of a page within a Sophie “book” would only take a few mouse clicks.
An open source multimedia assembling program is always welcome. Sophie will be particularly good at doing difficult things the easy way, and that is a bonus in an industry cluttered with “advanced” applications that seem to be going in the opposite direction. Given the proper planetary alignment, a nurturing community could grow around the development of extensions and additions to the program. Eventually, Sophie would be unrecognizable, and that is the best thing that can happen to an evolving living thing.
Did I mention that the application has also been conceived as a platform independent application for collaborative multimedia assembling? That’s right; Sophie would eventually allow people to join efforts in authoring and managing complex documents over a network. These are my kind of toys: evolving multimedia artifacts, born on a network, raised by a virtual village, and assembled with a tool that is being develop along similar principles. Very cool stuff.
Strategically speaking, however, the development of Sophie, and the model of collaborative multimedia creation in general, could be better implemented using the notion of software as a service. Downloading an application that would reside in the desktop and then using it to handle files over a network is relatively cumbersome. This model requires periodic updating of the program and a high volume of general traffic up and down the servers.
Under the current paradigm, Sophie is being developed just like Microsoft Word but I would rather work on something more along the lines of Writely. An Ajax-based version of Sophie within a regular web browser like Firefox would maximize the networking capabilities of the application. Full assembly functionality could be hard to achieve this way, but in a tradeoff between fancy multimedia features and wider potential for collaboration I would tend to favor the latter. The evolutionary success of a networked book will depend on the qualities of the network rather than the features of the book.
Online collaboration can be achieved more efficiently by sideloading rather than constantly uploading and downloading files. In an ideal world we would only need to upload original raw files, and only once. Everything else would happen at the server level. Every user would have access to every file and any combination of files at every step during the assembling process, from any computer connected to the internet.
This late in its development, altering the nature of an application like Sophie at this radical level is too difficult. Perhaps the best way to go about it is to release a beta version of the program, in order to broaden its community of developers, and hope that a team of Ajax-savvy people decides to create a browser-based alternative interface for Sophie. In the meantime she should consider setting up a series of dates with the guys at Ajax13. I promise I won’t be jealous.

a chink in the armor of open source?

With the coming release of Sophie and our recent attendence at the Access 2 Knowledge conference, I find myself thinking about open source software development. The operating system Linux is often used as the shining example of the open source software movement. Slashdot reported an interesting ZDNet UK article, which quoted the head maintainer of the Linux production kernal, Andrew Morton, saying that he is concerned about the large number of long standing bugs in the 2.6 kernal. Software always has bugs being worked out, even the long standing ones that Morton describes. Therefore, the statement is not all that shocking or surprising.
What intrigued me was this following statement:
“One problem is that few developers are motivated to work on bugs, according to Morton. This is particularly a problem for bugs that affect old computers or peripherals, as kernel developers working for corporations don’t tend to care about out-of-date hardware, he said. Nowadays, many kernel developers are employed by IT companies, such as hardware manufacturers, which can cause problems as they can mainly be motivated by self-interest.
“If you’re a company that employs a kernel maintainer, you don’t have an interest in working on a five-year-old peripheral that no one is selling any more. I can understand that, but it is a problem as people are still using that hardware. The presence of that bug affects the whole kernel process, and can hold up the kernel — as there are bugs, but no one is fixing them,” said Morton.
Keeping contributors motivated is crucial to open source endeavors. Reputation is a major factor in what drives people to submit code to the Linux development team. In retrospect, the importance of adding code for new features over adding mundane code for bug fixes, as part of reputation building makes sense. The street cred for fixing old bugs does not seem to be sexy enough; eventhough, some of these bugs could have long term effects on the quality of the Linux OS.
Are there solutions? One solution posited by Morton is to dedicate the entire next release to fixing long standing bugs. Although it is not clear to me how open source developers would react to this constraint. Another solution might try to expand the talent pool by encouraging young, gifted (even student) programmers to work on the bugs. Their motivations might be different from current developers, and any kind of participation might offer enough motivation.
Open source software development is still a fairly new phenomenon and is far from being completely understood. As we see more clearly how motivation factors work and what they produce in the open source production model, it will be increasingly important to document, analyze and learn from these observations. The future sustainability for open source software will rely on learning how to best maintain the developers’ incentives to contribute code. Therefore, we must remind ourselves that the open source development movement is something that must be continuously nurtured. And while we can cite Linux as a success story, the project itself is not on autopilot, nor will it ever be.

sophie is coming!

SophieIntro.gifThough we haven’t talked much about it here, the Institute is dedicated to practice in addition to the theory we regularly spout here. In July, the Institute will release Sophie, our first piece of software. Sophie is an open-source platform for creating and reading electronic books for the networked environment. It will facilitate the construction of documents that use multimedia and time in ways that are currently difficult, if not impossible, with today’s software. We spend a fair amount of time talking about what electronic books and documents should do on this blog. Hopefully, many of these ideas will be realized in Sophie.

A beta release for Sophie will be upon us before we know it, and readers of this blog will be hearing (and seeing) more about it in the future. We’re excited about what we’ve seen Sophie do so far; soon you’ll be able to see too. Until then, we can offer you this 13-page PDF that attempts to explain exactly what Sophie is, the problems that it was created to solve, and what it will do. An HTML version of this will be arriving shortly, and there will soon be a Sophie version. There’s also, should you be especially curious, a second 5-page PDF that explains Sophie’s pedigree: a quick history of some of the ideas and software that informed Sophie’s design.

a better boom?

An editorial in today’s New York Times by The Search author Jon Battelle makes the argument that the current resurgence in technology stocks is not the sign of another technology “bubble,” but rather an indication that companies have finally figured out how to capitalize on the internet. Batelle writes:
… we are witnessing the Web’s second coming, and it’s even got a name, “Web 2.0” – although exactly what that moniker stands for is the topic of debate in the technology industry. For most it signifies a new way of starting and running companies – with less capital, more focus on the customer and a far more open business model when it comes to working with others. Archetypal Web 2.0 companies include Flickr, a photo sharing site; Bloglines, a blog reading service; and MySpace, a music and social networking site.
In other words, Batelle is pointing out that one way to “get it right” is not to sell content to users, but rather to give them the opportunity to create and search their own content. This is not only good business sense, he says, it’s also more enlightened — the creators of social software such as Flickr are motivated equally by a desire to “do good in the world” and a desire to make money. “The culture of Web 2.0 is, in fact, decidedly missionary,” Batelle writes, “from the communitarian ethos of Craigslist to Google’s informal motto, ‘don’t be evil.'”
O.K. Doing good while making money. Reading this, I’m reminded of Paul Hawken’s Natural Capitalism and the larger sustainability movement — the optimistic philosophy that weaves together environmental ethics and profitability. But is that what’s really going on here? Isn’t the “missionary” culture of the internet a bit OLDER than Web 2.0? Batelle is suggesting that Internet capitalists have gotten all misty and utopian; isn’t it the case that some of the folks who were already misty and utopian have just started making some money?
I guess the more viable comparison here would be to Marc Andreessen’s decision to transform his Mosaic browser from its public-domain University of Illinois incarnation into the Netscape Browser. Andreessen certainly started out as a browser missionary — and, like the companies Batelle sees as characteristic of Internet 2.0, Andreessen’s vision for Netscape (and in the beginning, Jim Clark’s vision as well) was a strong customer focus and open business model. What happened? Netscape’s meteoric success helped inflate the internet “bubble” Batelle’s referring to, and in the end, after the long battle with Microsoft, the company’s misfortunes helped to burst that bubble as well.
So what paradigm fits? Is “Internet 2.0” really new and more socially enlightened? Or are we just seeing a group of social software businesses — and one big search engine — just in the early stages of an inevitable transformation into corporations that are less interested in doing good than making money?
Incidentally, last month, Marc Andressen launched a social networking platform called Ning.

the fly — a hundred dollar “pentop” for the overdeveloped world

flypen.jpg Two products that will most likely never be owned by the same teenager: The hundred dollar Laptop from MIT and the hundred dollar “pentop” computerized pen called the Fly. While the hundred dollar laptop (as we’ve said a few times on this site already) is promoted as a device to bring children of underdeveloped countries into the silicon era, the Fly is a device that will help technology-saturated 8 to 14 year olds keep track of soccer practice, learn to read, and solve arithmetic equations. Equipped with a microphone and OCR software, the Fly will read aloud what you write: if you use the special paper that comes with the product, you can draw a calculator and the calculator becomes functional. It’s all very Harold and the Purple Crayon .
In his review of the Fly’s capabilities in todays New York Times, David Pogue is largely enthusiastic about the device, finding it both practical and appealing (if a tad buggy in its original version). Most of all, he seems to think the Fly’s too-cool-for-school additional features are necessary innovation in a market that he says has begun to dry up — digital educational products for children. According to Pogue:
When it comes to children’s technology, a sort of post-educational age has dawned. Last year, Americans bought only one-third as much educational software as they did in 2000. Once highflying children’s software companies have dwindled or disappeared. The magazine once called Children’s Software Review is now named Children’s Technology Review, and over half of its coverage now is dedicated to entertainment titles (for Game Boy, PlayStation and the like) that have no educational component.
If Pogue is right, and educational software is on its way out, does this mean that everything has moved over to the web? And what implication does this downturn have for the hundred dollar laptop project?

powerpoint in transition

Hi, this is from Ray Cha, and I’ve just joined the folks at the Institute after working in various areas of commerical and educational new media. I also spend a lot of time thinking about the interplay between culture and technology. I read a small tidbit in this week’s Time magazine about PowerPoint and thought it would be a good topic for my first post.
Whether you love it (David Byrne) or hate it (Edward Tufte), PowerPoint is the industry standard presentation tool. Microsoft is gearing up to launch its long overdue PowerPoint upgrade in 2006. Time reports 400 million people use the application, and in a single day, 30 million presentations are given using it. Although the PowerPoint handout is still common, presentations are commonly created and showed only in a digital format. The presentation is a great example of how a medium goes through the process of becoming digitized.
When Microsoft purchased PowerPoint and its creator Forethought in 1987, presentations were shown on the once standard overhead projector and acetate slides. With PowerPoint’s Windows and DOS release, the software quickly replaced painstaking tedious letter transfers. However, PowerPoint presentations were still printed on expensive transparencies to be used with overhead projectors throughout the 1990s. As digital projectors became less expensive and more common in conference rooms, acetate slides became a rarity as the hand written letter did in the age of email.
Presentations were an obvious candidate to pioneer the transition into digital text. As stated, presentations were time intensive and expensive to produce and are often given off site. Therefore, a demand existed to improve on the standard way of creating and delivering presentations. I will also go out on a limb and also suggest that people did not have the emotional connection as they do with books, making the transition easier. In terms of the technological transfer, presentation creators already had desktop computers when PowerPoint was released with MS Office in 1990. By printing their PowerPoint output onto transparencies, display compatibility was not an issue. The PowerPoint user base could grow as the digital projector market expanded more slowly. This growth encouraged organizations to adapt to digital projectors as well. Overhead and digital projectors are a shared resource, therefore an organization only needs one project per conference room. These factors lead to fast track adoption. In contrast, ebook hardware is not efficiently shared, people have an emotional bond with paper-based books, and far fewer people write books than presentations. Only when handheld displays become as common and functional as mobile phones, will the days of paper handouts will be numbered.
Moving to a digital format has negative effects as mentioned by critics such as Tufte. Transferring each letter by hand did encourage text to concise and to the point. Also, transparencies were expensive as compared to PowerPoint slides, where the cost of the marginal slide is effectively zero, which is why we are often subjected to painstakingly long PowerPoint presentation. Although, these same critics argue that valuable time is wasted now in the infinite fiddling that occurs in the production of PowerPoint presentations at the expense of thinking about and developing content.
The development of the digital presentation begins to show the factors required to transfer text into a digital medium. Having an existing user base, a clear advantage in terms of cost and capability, the ability to allow users to use existing technology to either create or display the text, all start to reveal insight on how a printed text transforms into a digital medium.

no laptop left behind

100 dollar laptop little.jpg MIT has re-dubbed its $100 Laptop Project “One Laptop Per Child.” It’s probably a good sign that they’ve gotten children into the picture, but like many a program with sunny-sounding names and lofty goals, it may actually contain something less sweet. The hundred-dollar laptop is about bringing affordable computer technology to the developing world. But the focus so far has been almost entirely on the hardware, the packaging. Presumably what will fit into this fancy packaging is educational software, electronic textbooks and the like. But we aren’t hearing a whole lot about this. Nor are we hearing much about how teachers with little or no experience with computers will be able to make use of this powerful new tool.
The headlines tell of a revolution in the making: “Crank It Up: Design of $100 Laptop for the World’s Children Unveiled” or “Argentina Joins MIT’s Low-Cost Laptop Plan: Ministry of Education is ordering between 500,000 to 1 million.” Conspicuously absent are headlines like “Web-Based Curriculum in Development For Hundred Dollar Laptops” or “Argentine Teachers Go On Tech Tutorial Retreats, Discuss Pros and Cons of Technology in the Classroom.”
laptop-screenbig.jpg
Help! Help! We’re sinking!
This emphasis on the package, on the shell, makes me think of the Container Store. Anyone who has ever shopped at the Container Store knows that it is devoted entirely to empty things. Shelves, bins, baskets, boxes, jars, tubs, and crates. Empty vessels to organize and contain all the bric-a-brac, the creeping piles of crap that we accumulate in our lives. Shopping there is a weirdly existential affair. Passing through aisles of hollow objects, your mind filling them with uses, needs, pressing abundances. The store’s slogan “contain yourself” speaks volumes about a culture in the advanced stages of consumption-induced distress. The whole store is a cry for help! Or maybe a sedative. There’s no question that the Container Store sells useful things, providing solutions to a problem we undoubtedly have. But that’s just the point. We had to create the problem first.
I worry that One Laptop Per Child is providing a solution where there isn’t a problem. Open up the Container Store in Malawi and people there would scratch their heads. Who has so much crap that they need an entire superstore devoted to selling containers? Of course, there is no shortage of problems in these parts of the world. One need not bother listing them. But the hundred-dollar laptop won’t seek to solve these problems directly. It’s focused instead on a much grander (and vaguer) challenge: to bridge the “digital divide.” The digital divide — that catch-all bogey, the defeat of which would solve every problem in its wake. But beware of cure-all tonics. Beware of hucksters pulling into the dusty frontier town with a shiny new box promising to end all woe.
A more devastating analogy was recently drawn between MIT’s hundred dollar laptops and pharmaceutical companies peddling baby formula to the developing world, a move that has made the industries billions while spreading malnutrition and starvation.

Breastfeeding not only provides nutrition, but also provides immunity to the babies. Of course, for a baby whose mother cannot produce milk, formula is better than starvation. But often the mothers stop producing milk only after getting started on formula. The initial amount is given free to the mothers in the poor parts of the world and they are told that formula is much much better than breast milk. So when the free amount is over and the mother is no longer lactating, the formula has to be bought. Since it is expensive, soon the formula is severely diluted until the infant is receiving practically no nutrition and is slowly starving to death.
…Babies are important when it comes to profits for the peddlers of formula. But there are only so many babies in the developed world. For real profit, they have to tap into the babies of the under-developed world. All with the best of intentions, of course: to help the babies of the poor parts of the world because there is a “formula divide.” Why should only the rich “gain” from the wonderful benefits of baby formula?

Which brings us back to laptops:

Hundreds of millions of dollars which could have been more useful in providing primary education would instead end up in the pockets of hardware manufacturers and software giants. Sure a few children will become computer-savvy, but the cost of this will be borne by the millions of children who will suffer from a lack of education.

Ethan Zuckerman, a passionate advocate for bringing technology to the margins, was recently able to corner hundred-dollar laptop project director Nicholas Negroponte for a couple of hours and got some details on what is going on. He talks at great length here about the design of the laptop itself, from the monitor to the hand crank to the rubber gasket rim, and further down he touches briefly on some of the software being developed for it, including Alan Kay’s Squeak environment, which allows children to build their own electronic toys and games.
The open source movement is behind One Laptop Per Child in a big way, and with them comes the belief that if you give the kids tools, they will teach themselves and grope their way to success. It’s a lovely thought, and may prove true in some instances. But nothing can substitute for a good teacher. Or a good text. It’s easy to think dreamy thoughts about technology emptied of content — ready, like those aisles of containers, drawers and crates, to be filled with our hopes and anxieties, to be filled with little brown hands reaching for the stars. But that’s too easy. And more than a little dangerous.
Dropping cheap, well-designed laptops into disadvantaged classrooms around the world may make a lot of money for the manufacturers and earn brownie points for governments. And it’s a great feel-good story for everyone in the thousand-dollar laptop West. But it could make a mess on the ground.