3 ms·
There were many reasons why Hypercard died: Hypercard was very much a product of it's time. Software was far less complex so it was much easier to create a ge
by II2II 7y ago
There were many reasons why Hypercard died:
Hypercard was very much a product of it's time. Software was far less complex so it was much easier to create a general purpose development tool for end users. The author argues that attempts to recreate Hypercard try to do too much, that is because users expect more of software today. To give you an idea of what I mean: I used Hypercard to create a cookbook for a family member in the mid-1990's. You could enter recipes, search for recipes, and even export them to HTML. While this would have been an amazing accomplishment a few years earlier, the program was a relic of a bygone era the moment that it was written. Adding useful features, such as uploading those HTML files to a web server, may have been possible but would have required extensions to the language. Plenty of extensions existed, which is how companies like Cyan managed to produce an amazing for the time multimedia game (Myst) on what most people viewed as a stack of programmable black and white index cards. Yet extending Hypercard to reflect the technology of the 1990's would have transformed a product for everyone to an incomprehensible mass for anyone aside from developers. And the 1990's were primitive compared to the 2010's, never mind the coming 2020's.
In a similar vein, people's interests changed. The mid-1990's brought the web, so people were far more interested in developing for the web. The early days of web development were quite accessible, was focused upon content (much as Hypercard was) and allowed people to embed programs within that content (much as Hypercard did). While Hypercard may have been better for some things and certainly provided a better development environment, it was also obsolete.
As much as I loved Hypercard, the reality is that it was neglected rather than buried. It's longevity could have been improved without increasing complexity, such as adding colour or allowing multimedia files to be embedded (without resorting to third-party extensions). On the other hand, it would have died off eventually. The trajectory of web development shows how a once simple and accessible platform can become so complex that it takes a dedicated student to learn.
- scroot 7y agoAnother thing to think about is the metaphors used. Stacks, cards, and interactive objects on cards were really good metaphors that fit holistically in the Apple personal computing systems of the late 80s/90s. You're right that a lot of the computing environment has changed (eg the Internet is like a natural resource and should be assumed). Whether it is needfully more complex is another matter. A key question for designers today is this: what are the metaphors that would work for today's computing environments in a similarly holistic way, allowing users to become "authors"? This is something different than a modern Hypercard clone. I think when people want that old "Hypercard feeling," what they really want is this holistic nature, power, and ease of use for regular users -- not simple clones of the old thing.
- analog31 7y agoIndeed, even HC itself was limited to a subset of the full capabilities of the Mac of its day. To make a successful programming tool "for the rest of us" requires an intuition for what that subset should consist of, on the system where it will live. Too much stuff and it becomes prohibitive to learn. Too little, and it fizzles. Also, you had to be able to deliver enough value to a user, for them to forgive the aesthetics of your UI, and maybe even your mistakes. Bill Atkinson may have been a genius, or he may have gotten lucky. Or most likely, both. If you get the subset right, and make it compelling in other ways, then people will put up with the limitations and even creatively work around them. I think this explains the success of Visual Basic and even moreso, Excel. Within the context of pre-GUI computers, good old BASIC fits the model.