Tag: squeak

Of mice and pirates

, , , , ,

I had always understood patents to be about the mechanism of the device, not it’s effect. E.g., a particular mouse trap design, not the idea of catching mice.

But what do I know? Squeak blogger Torsten turned me on to this article about some courtroom pirates suing Apple over the User Interface in their latest operating system release. The original patent was for an old Xerox UI implemented in Interlisp-D, and now owned by a holding company.

Apple’s Tiger operating system isn’t implemented in Lisp. Do you suppose the lawyers are basing their argument on Greenspun’s Tenth Rule?

Brothers

, , , , , ,

I’ve admitted that I didn’t immediately get the point of the One Laptop Per Child project, but now I’m now very excited about the ideas behind this non-profit effort to build a $100 mesh-network computer to be owned by children in the developing world. This essay captures a lot of what I feel and wonder about it, including some fears of dystopian unexpected consequences.

Continue reading

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 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

intregration with document-oriented applications

, , ,

How do we integrate Croquet with the Web? How do we integrate with legacy applications in general?

We interact with computers now in a document model developed by Alan Kay’s Xerox PARC team a long time ago. (Xerox: The Document Company.) It is as is if we have our head bent over our desktop, looking at a piece of paper. We slide other pieces of paper in and out below the face of our bowed head. In Croquet, Kay’s team today lets us lift our head up off the desk and look up at the world around us, including our coworkers. But just as the 3D world has paper within it, shouldn’t the Croquet world have document-based software within it? Yes!

Continue reading

welcome Joshua!

, , ,

<%image(20050317-josh-gimped.jpg|400|400|Josh)%>We are excited to have a new developer joining us on Croquet at U.Wisconsin. Joshua Gargus is moving to Madison all the way from Atlanta, which is quite a big step for such a young man. And he and has wife had just bought a house in Georgia! Both my boss and I have moved our families cross-country for new jobs, including a period where our wives had stayed at the old house, and we know it’s not easy.

Joshua has already clearly dedicated his work to highly interactive applications on the cutting edge of technology. A haptic controller that lets you physically mold “digital clay,” including the ability to pull the molded surface out as well as merely pushing it in. (Think about it.) A sketchbook that recognizes individual strokes (not bitmaps) on a timeline for playback, annotation, and hardware rendering in various styles. Much of his work has been in Squeak, done at the leading centers for Squeak development. (Croquet is built on top of Squeak.)

I’ve looked at some of Joshua’s code, and I’m excited that we’re getting such a talented developer. Coming up: what we’ll both be working on…

Inventing the Future: information as a game

, , , ,

I’ve written before about how I’d like to never be forced to enter a name into Croquet. A consequence of achieving this is that you wouldn’t often need a keyboard. (A keyboard can be incredibly useful. I’m not proposing banishment. I just want to be able to get along without it. Also, there’s still access to legacy apps with their textual forms that need to be filled out.)

Croquet is built on the Squeak platform. This weekend I discovered that the older PlayStation II has an Ethernet adapter, the new one has it built in, that there’s a guy porting Squeak to the PS2, and that Croquet’s own Andreas Raab has demonstrated in the past that Squeak can be ported to the PS2. I’d sure love to have game boxes be Croquet information appliances.

Now add to that the ability to create content from within the Croquet environment itself, and think of kids creating their own connected persistent worlds. Screw the “information age”, it’s the “age of imagination”.

At C5, Croquet anchorman David Smith laid out a vision of Croquet running on an iPod-sized device connected to a heads-up display in your eyeglasses. (Never mind that by then, most folks who need vision correction will have laser surgery rather than glasses.) Noting that the basic technologies needed for this already exist today, and the pace of development and adoption over, say 20 years (c.f. the Apple Macintosh and what it has wrought), David feels comfortable looking at this sort of technology horizon. I’d like to see Croquet on a PS2 be a step in that direction.

Inventing the Future: learning the system

, , , , ,

Dear Diary,

I’m off to Japan Tuesday for the big conference. Better take a snapshot of what I’ve been doing, because I expect my world to change by the time I get back. My first six weeks on this radical Croquet project were spent with very general learning of what’s what. Drinking knowledge from a firehose. For the next six we’ve been prototyping some of the features from conference papers written by my boss, Julian, and his counterpart at U. Minnesota. We’re going to demo these at the conference, and we go on right after Alan Kay’s keynote address. Yikes. Good thing Julian gives great demos! I imagine the conference organizers know that and put him in that slot accordingly. (Cast of characters here).

[details below the fold]

Continue reading