Interactive Media Development

Topic of the day: the original PC concept... and the elements of programming

Today we look at 2 guys - Alan Kay and Casey Reas. 2 people who have (in their own way influenced the creation of interactive media. it's quite obvious really. otherwise i wouldn't have to blog about them). Alan Kay in particular wrote an article about what i would call the original PC concept. where the Dynabook (as he called it) would do everything a PC today can do (and perhaps a little more). the special thing is that Mr Kay wrote this a long while back - in the '70s to be precise - which is pretty ancient in terms of computer years (yes i think there's such a thing. considering how fast technology moves these days...)

So anyway enough background info... and awaaaaay we go...

1. Alan Kay's idea of the Dynabook is what most PCs are today. but what ARE the key features of today's PCs that Mr Kay was harping on about 30 years ago? I think (from what i can gather from the article anyway) that Alan envisioned the PC - personal computer. something where there would no longer be the need for time-sharing (which was the case back then).

There was also his vision of having a PC that had GUI (Graphic User Interface). basically Kay hoped for a computer where there would be visual output of a decent quality (good enough to rival print media in terms of contrast and quality). He also wanted it to have good audio output, and for the system to have almost instantaneous response to user commands (ie immediate feedback in terms of output).

I guess part of the ideal was to have a system that could do away with the need for paper (why else would he want something with visual quality equal to or better than print media?). Hence also the vision of the Dynabook working like a file cabinet to store all sorts of information.

Kay's vision of the Dynabook included content creation - using the Dynabook for various input and output purposes, like creating pictures, music and even programming animation. I think he envisioned it to be used for anything and everything, including simulation.

2. How much of Kay's vision has been realised? well i'd say most of it has been. today's computers are an indication enough of how much of the dream has become a reality. There's the storage, the input and output, and the GUI. pretty much describes today's computers, no? but not every part of the vision became reality. most notably the desire for instantaneous response to commands. Feedback has always been an issue with today's computer systems. one of the greatest complaints of users everywhere is the case of LAGGING, HANGING and CRASHING (in no particular order). and of course everyone's favourite nightmare - The BLUE SCREEN OF DEATH...(that's an oxymoron in itself.... since when does anyone have 'favourite nightmare'?!!!) granted these are the result of memory constraints, but are obvious indicators of the inability of today's computers to live up to Mr Kay's vision of instantaneous feedback and response.

and now, on to the article by Mr Reas...

3. Casey Reas talks about the aspects of programming. Dynamic form, gesture, behaviour, simulation, self-organisation and adaptation. Judging on how he defines all of them, i would say that each of these elements appears to have some importance in the process of interaction. each of these elements in their own way are part of the interactive process (that's what i think anyway). in terms of importance however, i'd say that Dynamic form, behaviour, simulation and adaptation would be the more important elements, as they reflect the process of interactivity.

4. There's a need for 'literacy' for policy makers regarding interactive media. Knowledge on both sides of the fence is necessary for policy effectiveness. If a policy maker doesn't know what the issues are regarding interactive media are, what would give him the right to make decisions (apart from his being appointed / hired to). I think it's a complaint that many people may have about parents. they complain their parents don't understand because they're not in the same position and can't identify with what the teenagers are going through. If you don't know what issues are important how can you make decisions? If you don't know why things are the way they do, what gives you a right to pass judgement?

5. I think that Jakob Nielsen (for some reason or other has a adversity to Flash programming - just like me come to think of it) has a valid point. There has always been a necessity for balance between core functionality and the 'bells and whistles' (what people call aesthetic elements). I guess that when over-use of the decorative elements distract the user from the main functions of the website. Or, even worse, the functionality and inteface of the website is compromised in the attempt by the programmer to throw in as many 'bells and whistles' to keep users entertained. how many times have you come across a really fancy-looking website with lots of cool graphics, animation and audio stuff, but at the same time has terrible user interface or even lags or hangs because it's trying to load up all the memory-consuming features. of course in good cases your PC lags. in bad cases, it hangs and you meet the programmer's worst nightmare - BSOD. I think Nielsen's point is valid - and should not be limited only to the area of flash programming. granted, it's always nice to have a good-looking and aesthetically pleasing website design, but eventually every thing boils down to good user interface. Sure, there's novelty value in all the little features, like how moving your cursor over something makes a 'cute-sounding' noise. but after a while it gets irritating don't you think?