Slashdot Mirror
HyperCard Gone for Good
Second to Last HyperCard Goddess writes "HyperCard has finally been removed from the Apple website. Read some comments about the passing. I read about HyperCard's demise on the RunRevolution list. It's pretty sad; the unexpected part was that it remained for sale at the Apple Store for six years without an update. Although we've all moved on, we'll certainly miss it." I won't.
While I used it all the time in middle school, I had managed to completely forget that this application ever existed. All of a sudden I wish I could look at all the games and stuff I used to make with this. I think after learning basic this was the next 'programming' language/tool I ever used.
Apple should really think about releasing the source code and letting the OS community take it over. HyperCard was a great development environment, and I really think it influenced the way current environments work. HyperTalk was the first language that I learned on the Mac, and it was my second overall language, first being AppleSoft BASIC. Rick
The only "software" I ever created from scratch was HyperCard-based. I built a guitar tuner and a lotto game player (input state rules to a randomizer), both of which got a decent number of Compuserve downloads back in the day. I also used to hand out a version of my resume as a browsable stack, which was kind of cool and helped me get a few Mac-related jobs as well.
Of course, I stopped writing stacks entirely by about 1991 or so, and haven't written more than a shell script since. But I still have fond memories of it as a tool and environment. It's a pity that HyperCard died when it did (really about 10 years ago), but it was always the "neither fish nor foul" of Apple products.
That and Pippin.
-- Josh Turiel
"2. Do not eat iPod Shuffle."
On a side note, my good friend recently joked about a 'skinny' port of Hypercard for the iPod. GID input might be a pain, though scrolling through buttons/fields might work?
I hate Grammar Nazi's
I was surprised while reading about the death of Hypercard (like 3 days ago, way to stay on top of things Slashdot) to find that Myst was written in Hypercard.
Not that Myst is anything special, I hated that damn game. But still, its interesting to note.
It was actually a nice introduction to object-oriented programming. Everything was addressed as an object, and events were passed as messages sent to objects.
HyperTalk, the HyperCard programming language, was the predecessor to AppleScript. Lessons learned from HyperTalk were factored into the design of AppleScript, in particular the langauge extensibility features. As a result, AppleScript suffered somewhat from second-system effect.
A lot of people also used HyperCard as a database. Many tasks that people use FileMaker Pro for today could be done with HyperCard.
I can't believe that Hypercard was still was just recently killed. I always thought that Hypercard was WAY more powerful than people let on. It was really the Mac OS of programming. On the surface level, it was an easy to use, fairly limited, programming environment. What most people didn't know though is that Hypercard was capable of just about anything any other language could do at the time. The "guts" of Hypercard were hidden from the user (and most programmers), but with some effort you could have a tool that was flexible as hell.
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 is the magic number.
I had a teacher when I was in 7th grade (1990?) that used a Laserdisc player, Hypercard and a projector to teach us life science. All of his lectures revolved around that setup. That was my first major exposure to a Mac. He had the Mac controlling the Laserdisc player and everything. Hypercard will be missed.
The closest I ever really saw to Hypercard on the PC was IBM Linkway. I played with it briefly, and it just couldn't compete with Hypercard.
It always struck me as odd that Apple kept hypercard around all these years, after all even Appleworks got more updates, and given that when Apple moved to OS X, they killed off a lot of calssic stuff (and steve's declaration of the death of classic) it seemed odd they would keep it arround.
I wonder if we may see the next generation of hypercard from Apple in the near future? Something like that would be an awsome addition to OS X, and it seems to me like it could be Apple's iLife version of Keynote.
T Money
World Domination with a plastic spoon since 1984
Hypercard was the wonderful creation of Bill Atkinson, along with MacPaint and Quickdraw. Although Bill spends most of his time now as professional photographer, and not actively programming for Apple, he still uses Hypercard every day. Rumor has it that Bill has the certain retained rights to at least a good sized portion of the source code of Hypercard, which become active if Apple does not actively sell Hypercard. While more recent features of Hypercard such as Quicktime 3.0 might remain Apple's property intellectually, I would be interested to see if Bill Atkinson would be interested in putting Hypercard core code out in the Open Source area for development. It would require at least some grudging cooperation by Apple. So, the fact Apple has dropped it from its active inventory may actually set part of Hypercard free sometime in the future.
The Hypercard environment suited a very iterative development style, perhaps more so than anything else that I have worked on since then. Data was automatically persistent. Switching from running a program to editing a method handler was just clicking on a graphics palette. You could be using a program, see something you don't like, click on a selection tool, click on something, and fix it.
... for each card in ... for item in .... set the script of it to ...." and it was all done.
It very much had the feeling of being able to tinker with the engine while the car is running. I suspect that working with Lisp Machines and Smalltalk environments was similar, but unfortunately I missed those boats. (except for being able to play around with Squeak now.)
My first professional software development job was writing a series Hypercard stacks. I remember one time realizing that I had hit an architectural dead end, and needed to refactor a bunch of methods (although I didn't learn the term refactor until much later.) I was lamenting having to make those changes all across all the code base until it suddenly hit me, I could write a hypercard script to make the changes. I put something home stack that said "for each backgroud
HyperCard 3.0 and Quicktime 3.0 were previewed about at the same time. Hypercard projects (known as "stacks") would have become Quicktime movies playeable on any QT player on Mac OS, Windows and that also in a Web Browser. Evidently that meant full color support and things like wired sprites and QT movies in stacks without add-ons. Somehow thats about where Hypercard got an accident and went on life-support. Maybe backward-compatibility became too much of a puzzle when they asked themselve what to do with xfcn and xcmd's support(native code add-ons). Maybe they were also pressured by Macromedia as they were pushing flash and shockwave for interactive web content. Ironically, Macromedia Director Shockwave Studio originated from VideoWorks, a linear sprite animation program on the Mac. Macromind (that's how they were called at the time) took VideoWork, renamed it Macromind Director and added "Lingo" wich was more or less a carbon-copy of HyperTalk, HyperCard's own scripting langage and messaging structure. Director had persistent data too, fields and buttons, but it had color, native sprite supports etc, but it cost 1000$. Until version 4.0, it was a Mac only app and I guess Apple lazyness in upgrading Hypercard to support color and multimedia features had ,among other things, something to do with Macromedia even before HC 3.0 was planned. Hypercard 3.0 +Quicktime 3.0 on the web was probably too much for Macromedia. Mr. Gates had probably something to say about it too, in a way QT 3.0 would have become too much of a "trojan-horse" in Windows. It should be noted that Quicktime for Windows already contains some parts of the Classic Mac OS API to emulate Quickdraw in PICT files and other things.
Anyhow HyperCard 3.0 never saw the light of the day and only some basic interactivity and the wired sprite feature was brought to QT 3.0. There is a single 3rd party app that can exploit all of the interactive features of Quicktime and its called LiveStage. Still, its very far from HC 3.0 could have been.
Another thing I have rarely seen mentioned about HC, is that it was used internally for many years by Apple so the interface designers could prototype their GUI without having to know about memory pointers and A-traps. Specialised Pascal and C++ programmers would then reproduce the layout and behavior using Mac OS APIs. Many widgets, dialogs and control panels in Mac OS 6-8.x were designed and prototyped in Hypercard. I guess than Interface Builder and AppleScript Studio (please rename this Apple) fulfill the same goal today internally for Mac OS X interfaces.
As for Myst, not only Hypercard was used to build the first Myst, it was the inspiration for the game itself. One thing so easy to do with HC right from the start were point and click adventures. I'm sure that I'm not the only one to have started to build (and never finished) a point-and-click black and white adventure game in HC before Myst was out. I guess the Authors from the start had the idea of doing an "hypercard point and click adventure using rendered graphics and qt movies". Hypercard limitations made the game what it is (for better or worse, but mostly the better). Also precursor to Myst and inspired by HyperCard is Cosmic-Osmo, one of the very first cd-rom game (also from Cyan). It ran on HC with a Macromind VideoWorks extension for animation. For those who don't know Cosmic-Osmo, it's a fun wacky adventure game with no goal where weird things happens when you click on things. You can go thru mouse holes and water drains and warp from place to place with secret passages. Oh well tha post is getting wacky too, let's end it here. HyperCard is Dead, long live HyperCard!
Buzzy Beetle
We had a HyperCard product that filled a niche. It was perfect. It sold like hotcakes at the state fair on a sunny morning.
We kept getting inquiries: when is the Windows version coming?
We'd been told by Apple that a Windows version was in the works, and that the way they were going to do this was to build on top of QuickTime, which was already cross-platform. It was about a year overdue and we were getting anxious, so I cornered one of the main HyperCard guys at WWDC and asked him (1) why he was presenting on technologies other than HyperCard and (2) what was up with the QuickTime-based port. As you've probably guessed, the two were related.
The company lasted another six months, then we closed the doors because HyperCard just wasn't keeping up with what people expected. It just languished away.
If Apple had come through with a cross-platform HyperCard which made QuickTime programming accessible to non-programmers, it might have been killer. Might have been.
It has been dead for years they have only just now gotten around to writing the obituary.
In its day Hypercard was an easy to learn and fairly powerful programming language that anyone could use to pump out very Mac like applications.
The problem was that Hypercard did not keep pace with the Macs it was running on. Color was slow in coming as well as support for features that were added to the OS. Back in the day it was the defacto standard for Mac multimedia CD's.
If Apple had kept development of hypercard on the same pace as the MacOS, hypercard would have been a killer program under OS X. Who knows how far it might have gone. Hypercard with access to all the goodies that OS X has to offer like a shell to UNIX, etc. might have been very powerful. Maybe even integration to the Xcode tools might have produced compact, fast, standalone applications without the need for a player app.
Many people have tried to fill Apples shoes with programs like supercard and revolution but none had the knack of producing good programs like Apple.
I am sad to see it go. It could have been so much more than it was. Too bad Apple did not notice the diamond in the rough that it had.