Why Hypercard had to die (2011)
loper-os.org
loper-os.org
You've got silly little animations[2], sound samplers[3], choose-your-own adventure stories[4], reference guides[5] and teaching materials[6]. But there's so much more in the collection.
I thoroughly recommend that those unfamiliar with HyperCard have a browse of the collection and see what was made possible by this groundbreaking 1980s tool.
I'm always looking for more stacks for the collection - if anyone reading this has any (either already as digital files or on floppy disks), please do email me: HyperCardOnline@gmail.com
[1] https://archive.org/details/hypercardstacks
[2] https://archive.org/details/hypercard_computer_sind_doof
[3] https://archive.org/details/hypercard_cheapsequencersit
[4] https://archive.org/details/hypercard_inigo_gets_out
[5] https://archive.org/details/hypercard_macprinters-11
[6] https://archive.org/details/hypercard_usgs---teaching-earth-...
Point I'm making is that hypercard gave access to absolutely everyone. Which means it was used far outside the normal niche technical interests.
It's sort of a neat archaeological dig into the mind of a broad spectrum of people at the time. Rather than a slice of niche technical individuals.
[1] https://news.ycombinator.com/item?id=22285675
Do you have the first commercial HyperCard stack ever released: the HyperCard SmutStack? Or SmutStack II, the Carnal Knowledge Navigator, both by Chuck Farnham?
SmutStack was the first commercial HyperCard product available at rollout, released two weeks before HyperCard went public at a MacWorld Expo, cost $15, and made a lot of money (according to Chuck). SmutStack 2, the Carnal Knowledge Navigator, had every type of sexual adventure you could imagine in it, including information about gays, lesbians, transgendered, HIV, safer sex, etc. Chuck was also the marketing guy for Mac Playmate, which got him on Geraldo, and sued by Playboy.
https://www.zdnet.com/article/could-the-ios-app-be-the-21st-...
>Smut Stack. One of the first commercial stacks available at the launch of HyperCard was Smut Stack, a hilarious collection (if you were in sixth grade) of somewhat naughty images that would make joke, present a popup image, or a fart sound when the viewer clicked on them. The author was Chuck Farnham of Chuck's Weird World fame.
>How did he do it? After all, HyperCard was a major secret down at Cupertino, even at that time before the wall of silence went up around Apple.
>It seems that Farnham was walking around the San Jose flea market in the spring of 1987 and spotted a couple of used Macs for sale. He was told that they were broken. Carting them home, he got them running and discovered several early builds of HyperCard as well as its programming environment. Fooling around with the program, he was able to build the Smut Stack, which sold out at the Boston Macworld Expo, being one of the only commercial stacks available at the show.
https://archive.org/stream/MacWorld_9008_August_1990/MacWorl...
Page 69 of https://archive.org/stream/MacWorld_9008_August_1990
>Famham's Choice
>This staunch defender was none other than Chuck Farnham, whom readers of this column will remember as the self-appointed gadfly known for rooting around in Apple’s trash cans. One of Farnham ’s myriad enterprises is Digital Deviations, whose products include the infamous SmutStack, the Carnal Knowledge Navigator, and the multiple-disk set Sounds of Susan. The last comes in two versions: a $15 disk of generic sex noises and, for $10 more, a personalized version in which the talented Susan moans and groans using your name. I am not making this up.
>Farnham is frank about his participation in the Macintosh smut trade. “The problem with porno is generic,” he says, sounding for the briefest moment like Oliver Wendell Holmes. “When you do it, you have to make a commitment ... say you did it and say it’s yours. Most people would not stand up in front of God and country and say, ‘It’s mine.’ I don’t mind being called Mr. Scum Bag.”
>On the other hand, he admits cheerily, “There’s a huge market for sex stuff.” This despite the lack of true eroticism. “It’s a novelty,” says Farnham. Sort of the software equivalent of those ballpoint pens with the picture of a woman with a disappearing bikini.
https://archive.org/stream/NewComputerExpress110/NewComputer...
Page 18 of https://archive.org/stream/NewComputerExpress110
>“Chuck developed the first commercial stack, the Smutstack, which was released two weeks before HyperCard went public at a MacWorld Expo. He’s embarrassed how much money a silly collection of sounds, cartoons, and scans of naked women brought in. His later version, the Carnal Knowledge Navigator, was also a hit.
[2] Easter Memories: Jesus Farnham on the Golden Gate Bridge Easter 1996:
(Yes, there were post-1987 updates, none of which added fundamental critical features like color support. Which was introduced to the Mac lineup with the Mac II, also in 1987.)
Also, Steve Jobs wasn't even at Apple for the critical phase of HyperCard's life cycle. By the time he returned in 1997 there had been no meaningful investment in HyperCard for many years, and it's lack of a native networking paradigm meant that even if Apple had thrown their weight behind it, it would not have been possible to catch up to the web which was already well past critical mass at that point.
By the time they could have mustered any serious effort to save it, the web had already won.
Edit: Myst apparently used a plug-in (InColor from Heizer Software), and 2.3 officially added Color Tools
https://orangejuiceliberationfront.com/how-hypercard-got-its...
But actually, looking at Wikipedia, it appears there was work on a Hypercard 3.0, which added a bunch of features and turned Hypercard stacks into a special kind of Quicktime movie. It was demoed as alpha quality and never finished... which sounds pretty much exactly like nearly all other Apple products at the time! Smart people doing cool stuff with little direction under bad management, unable to get the cool stuff out the door. And arguably by the return of Jobs, the ship had sailed. There was no way Hypercard was going to take over the world after the introduction of Windows 95 and WWW, that was clear to anyone. I wish it had, though.
https://donhopkins.medium.com/focusing-is-about-saying-no-st...
I never made anything even close to "commercial-ready", but I had a lot of fun doing it. It felt like within a day or two, you could figure out how to make buttons and event mappings, and I thought it was so cool that you could easily animate things in the form of movie clips without having to finagle with cycling through sprites. I made simple point and click adventures, interactive menus, and once I took physics and calculus in high school, a very simple platformer. It was a lot of fun.
Nowadays the closest thing I've found for a similar level of easiness is GameMaker Studio, and I have a copy (legitimate this time :) ), and it's fun to play with, but it still feels more complicated than it needs to be. With Flash, I never had to learn about shader programming or anything like that. To be clear, I'm not trying to knock GameMaker for this, it's a great tool, it's just not as simple as Flash, for better or worse.
Obviously Flash Player needed to die, and I'm not suggesting we resurrect it. It was a horrible buggy mess a lot of the time (especially on non-Windows platforms in my experience), but I don't feel like we've really "replaced" it fully yet, at least not on the development side.
Hypercard was a bit before my time, sadly (we didn't have a working Mac in the 90s), but it looks like something I would have really enjoyed playing with.
I haven't used it in like 6 years, so my knowledge is fairly out of date, but if I remember correctly, it's kind of lacking my favorite feature from Flash: the ability to use a professional-grade animation tool directly within the program. No messing with exporting sprite sheets or a series of bitmaps or anything, you can just create a movie clip, double click it, animate it, go back, and click "export to code". It's a true "one-stop-shop" for doing almost everything in your project.
GameMaker actually has a pretty-ok sprite animation system built in, good enough for most retro-style games, but it's still pretty weak compared to Flash for anything more complex.
https://www.construct.net/en/make-games/manuals/construct-3/...
Maybe I need to play with Construct again though, it's probably improved substantially in six years.
Even still, I don't believe I can export directly to anything supported nowadays, right? Does the HTML5 exporter work?
edit: Looking more closely, I do now see that you have to manually convert the AS3 when exporting to HTML5. That’s a bummer.
Somewhat ironically, due to something like Ruffle, exporting to an SWF like before might actually be a viable option again, since you'd get all the nice sandboxing of modern browsers while having pretty-ok flash compatibility.
"Get Animate as part of Adobe Creative Cloud for just US$20.99/mo." from https://www.adobe.com/products/animate.html
It would be a hard thing to ask various professions that developed content using HyperCard to fork over the money.
As much as I appreciated having more advanced tools like Unity later in my career, you can't beat the self discovery that was possible with Flash.
I have seen this pattern repeat several times over in my life: programming personal computers with BASIC in the 1980's and web development in the late 1990's are the most obvious examples. HyperCard sort of fits in between since it was one of the more accessible GUI development tools, though it was by no means the only one.
Building a blog, a news website, a niche web app, or the new Facebook, it nearly doesn't matter, you must use the latest state of art tools. We have completely lost all the intermediate levels between beginner and professional.
Sometimes it's justified as an unfortunate effect of the internet for sites and apps handling personal and sensitive data, something that the semi-professional 90's shareware didn't have to deal with. But I feel like that doesn't explain it all.
That said, Pico-8 is (purposefully) limited pretty substantially. You can only have like 32kb of RAM, you are really limited in your sprite size, and I think the built-in editor is kind of annoying.
Flash was fun because it was super easy to get into, but it kind of felt like a "big kid" programming environment. While I know the performance wasn't great, outside of that I never felt limited by Flash.
But as far as I can tell, there's no one trying to recreate Flash the authoring program. Which is a big shame IMO. We need something that enables creativity with a low barrier to entry.
But as you say - back in the old days, the truly important thing had nothing to do with the runtime, and had everything to do with the authoring program.
Someone really needs to build something similar, and - because we're starting in a later era, the only influence it needs to take from flash lies in the UI/UX.
It could use the SWF file format too, there's nothing wrong with that IMO, and there already are many tools built around it.
As I said, I do think GameMaker is a reasonable enough substitute for stuff. While I find having to write shaders a bit irritating, you don't have to do it very often, and you can get up and running in a fairly short amount of time, and it's HTML5 exporter works pretty much perfectly from what I've played with. Is it as easy as Flash? No, but it's still a pretty low barrier-to-entry for people, I think I could probably teach a kid how to use it and they'd pick up the basics.
IMO it is too high. People who are not very much into tech are easily scared away by the need to write any code.
The thing with Flash is that when you launch it and create a new project, it looks, feels and works like a vector graphics editor — because it is one, and a very good one. You start drawing stuff. You start animating stuff. If all you want to make is a cartoon, ActionScript is entirely optional. But then you start wanting to add buttons that do simple things like "go to frame X". You copy-paste ActionScript for that. You go deeper and deeper into the ActionScript rabbit hole. Before you've realized it, you're coding complex logic for a game.
Flash lures you into wanting to write code by being an extremely easy to use animation editor. GameMaker repulses you by making writing code a prerequisite for going any further.
They should and open source it.
It’s also completely possible to run your own code today on a Mac, so we would have to believe that Jobs was only out to get the in-house easy to use programming language.
More likely is that Jobs wanted to use work from NextStep for OSX which would mean rewriting HyperCard to work with NextStep, and Apple wasn’t exactly flush with cash when Jobs returned.
One of the commenters notes that there was a clone for NextStep called “HyperSense” which failed to sell. So another possibility here is that HyperCard just wasn’t as popular as we’d want it to be.
The Apple ][ shipped with BASIC. Apple was not founded on letting you consume your computer.
But the world had changed since the 1970's and there was a software ecosystem.
Hypercard would seem to have brought programming to the masses. But by then there was a broad base of software companies that would provide users the calculator app, etc. This leaves Hypercard, like BASIC before it, a rather more beautiful and modern tool for nerds.
And you can tell Jobs always had an uneasy relationship with nerds. :-)
Famously, when he returned to Apple, he used NeXTSTEP/OpenStep instead of a Mac until Mac OS X 10.1 came out and it was stable enough for production use. I can't find the article, but someone received an email from him around 2000 where the headers said NeXTMail.
iWork suite didn't become "free" until 2013, and even then you have to buy a new mac or iOS device (so for example, given that I bought my mac used, I'd have to buy it new)
Correction: Apple charges a premium for their computers because that premium pays for all the software packages they include with it. XCode, Keynote, Pages, Numbers, etc... None of that is included in Windows but I can buy a fully usable by most people Windows laptop for $299 vs the cheapest Mac laptop is $999. Of course some of that $700 difference is that Mac is a better piece of hardware but much of it is you're paying for all the extra software.
BTW: If I could choose to buy a Mac for $200-$300 less without most of the extra software I would since I don't use any of it.
no, you're paying $999 for the entire bundle of features that come with your Mac. That includes the software. It's not free any more than any other part of it is free.
These apps are functionally "complete." I think there's a pretty grey line between "you're paying for bundled software" and "Apple is just giving away these old things that cost them nothing to keep functional."
If you had a peek at the spreadsheet that lists the expenses of "macbook" (materials, TSMC fees, industrial design man-hours, OS programming hours, etc.), "Pages" would not be a $50 line item. And if Apple dropped that bundled software Macbooks wouldn't drop by $200 or whatever.
I don't think this was Apple's attempt to stifle the ability to code on your own computer. They shipped Project Builder on, what, day 1 of Mac OS X?
It's more likely that…
…this was not super popular, as what's the possible market for an app that builds applets that only work on Macs? Given Mac marketshare at the time, maybe not a lot of hobbyists who (a) wanted to make an app, but (b) didn't want to dive into building a full UIKit application.
…this thing was confusing to market. It's hard to give the 1-liner description of HyperCard.
…this got dropped because it was not part of the core focus of getting a next-generation operating system out the door.
…maybe they didn't actually know how to rewrite it for OS X? Like, did anyone know how the HyperTalk interpreter worked besides the guy who make it?
Carbon existed in OSX.
It seems to me the authors claim is that HyperCard did not belong to Jobs’s vision of a computer as basically an appliance. HyperCard fit better in a vision where a computer was more of a tool.
Mid-90s marketing: "Think Different" (fine, but many people don't like to think of themselves as "weird") and "It just works"
late 2000s, 2010s marketing: Straight up luxury branding. Aspirational, like a BMW, Mercedes, or a high end appliance.
I was a lover of hypercard. It seemed to rekindle some if the magic of AppleSoft BASIC when I moved from the Apple II to the Mac in elementary school. I remember being surprised at how difficult it was to program a Mac compared to an Apple II until I found HyperCard. It seemed full of possibility.
I'm inclined to agree. The word "annoying" would have worked about equally well without being as mean-spirited.
Sorry to spam, but I am working on a scripting language for the web based on HyperTalk, the scripting language from HyperCard, to try to recapture that magic:
<button _="on click transition my opacity to 0 then remove me">
Fade & Remove
</button>applescript is also based on hypertalk, and I believe it suffered being too wide open and unfocused
hyperscript is much more tightly focused on DOM manipulation and event handling, so my hope is that it doesn't suffer from the usability issues that can creep in when using AppleTalk
it's an experiment, so let's find out
You can sure say that again. I always found it difficult to write nontrivial AppleScript code, which could have been ameliorated had the IDE been anything other than worthless for debugging.
But yes, it’s very easy to read.
Yes it was cool, but there’s no conspiracy behind its demise. It died because the World Wide Web accomplished basically the same thing, not initially as elegantly or powerfully, but open and universal (and today, very much more capable than HyperCard was).
HyperCard usage declined and Apple gave up on it. It’s not complicated.
This is incorrect and I'm convinced that you agree after you think it little more. HyperCard was tool for non-programmers. Like spreadsheet. Web is not alternative to HyperCard. You have to learn web programming to do anything.
We should not get over it, but create replacement or recreate it.
But as with all simple things in tech, there are more people whose pay depends on complexity. And so Web 2.0 rose and CSS+JavaScript became what it is today.
(If anything, it's easier today to build a circa-2005 style site than it was in 2005! The native API has grown up enough that you don't need jQuery any more, and honestly good riddance.)
The trouble with the circa-2005 web is that it wasn't actually all that simple. You still had similar complexity to what people do today, but not very many ways to make that complexity manageable. So it was very easy to create situations in which things went wrong a lot and you couldn't really figure out why - something I think the rosy glow of nostalgia easily obscures, these days.
My early career, in hindsight, really was built on dealing with that kind of "unfixable" complexity, finding ways to reduce or replace it or at least make it more manageable - if often just in self-defense, as I typically was also largely responsible for maintaining the same stuff I built. The "capstone project" of that phase was something that we would today describe as an SPA, built in 2011 when the concept barely existed - I hadn't set out to (re)invent that wheel, nor did I even understand until a few years later that that was what I had done, but I found my way to it as the only reasonable option for coping with the essential complexity of the user interaction it expressed, and it worked really well!
That work was for one of our biggest contracts, which we were at risk of losing if I didn't find a way to fix their broken and unusable registration process. It would probably have sunk the company if I'd failed. Reworking it into an SPA avant la lettre solved the problem and saved the contract, and it was some of the hardest work I've ever done precisely because, at that time, there were no tools to help manage all that complexity. It's only gotten easier since then, as successive frameworks have built on prior work in removing accidental complexity and making essential complexity easier to express and manage.
Yes, today's tools are themselves more complicated than jQuery or whatever, sure. That's fair. You need to spend more time learning how to get the most out of them, that's also true. But the tools also do more, and largely do it in ways that are worth having.
A Bridgeport mill takes a lot more learning than a chisel, too, and you can do a lot more damage with a Bridgeport mill used wrongly. Used rightly, though, you can achieve far more with a Bridgeport mill, far more quickly and easily, than any chisel in the history of the world could ever let you do.
Sorry, but I don't see how that is at all different than "you have to learn the Hypercard scripting language to do anything."
It would be utterly risible to suggest that a child of similar age and prior experience could do the same today, starting from scratch with web technologies. Yes, you can do more with the modern web. But the initial complexity barrier is very much higher.
That’s after work his way through much of the book, of course, but... as with any complex domain, the right teacher can make a big difference.
That's not to say it isn't a significant accomplishment, and he should be proud of it!
It’s pretty much all the major elements of web programming but using the more elegant ways of simplifying the experience.
I’m not denying the complexity just saying that there are still many (particularly in Python or in cloud PaaSes) who value streamlining the experience.
I get the sense the book tries to surf the reader over the top of most of that ocean, and that's reasonable enough, but the ocean is still there. I wouldn't consider it all that comparable to Hypercard, which in this metaphor I guess is more like the town pool back when those still existed? People who are ready for the deep end can dive into it, and people who feel like paddling around in the shallow end is more their speed can safely do that too.
But that's building on close to twenty years of working in the field, and a bit over three decades since I first put my hands on an Apple IIe's keyboard and wrote
10 PRINT "HELLO"
20 GOTO 10
I feel that enough people complain about it not existing and then quickly proceed to not recreating it. If there was market for this, it would exist.
I've never used Hyper Card, but I guess that for prototyping of 'real software', programs like InVision work. Most of the trivial programs you could create with HyperCard (from the examples shown) can be recreated in other software (like excel or soulver) or already exist.
Don’t mistake the explosion of JavaScript land for being the same thing as the World Wide Web. Static websites are as easy to build now as they were in 1995, and in some ways easier.
> And if you think that XCode, Python, Processing, or the shit soup of HTML/Javascript/CSS are any kind of substitute for HyperCard, then read this post again.
The thing that made HyperCard great was that it wasn't very capable. Which made it approachable.
The standalone Interface Builder had palettes, which you could fill with custom objects. There were third party palettes that allowed non-programmers to click together and configure custom applications for specific domains.
There were palettes that extended the whole shebang with scripting languages so that you could also add custom logic in Interface Builder.
Unless you're saying that the most recent versions of Xcode don't do that, which would be news to me.
I agree that it's not well-used, but that's not the fault of Xcode. As far as I can tell it provides everything you'd need.
Not the same thing. At all. Not even close.
Palettes were final-packaged components that were at the same level as pre-built ones.
IBDesignable is a way for adding some interactivity to the views you are creating for an app while you're building said app. Like SwiftUI Previews. And it works about as well, that is not really at all.
With IBDesignable, Xcode was continually trying to build the entire dependency tree, meaning for example the entire Postscript interpreter. And failing >50% of the time, which then kills your view. I hear the same happens with SwiftUI previews once your project gets bigger. It certainly happened to me almost immediately when I was trying it out.
Again, they're not even close.
And still WWW had orders of magnitude more users almost immediately.
Hypercard is only easier to learn than "regular" programming languages if you're English speaker.
In 1995, putting together a website was easier than using Hypercard. And so people flocked to it. Even people who were already somewhat familiar with Hypercard. Even though, at the time, Hypercard was largely more powerful. Some of that was because the Web made it so much easier to share. But I don't think that's the whole story.
Fast forward 25 years, and the Web has become much more powerful, but the number of people making websites recreationally who don't also get paid to write software seems to have dropped precipitously.
i wouldn't call the web elegent or powerful today either
Of course it would be offensive to compare VB to HC, given that VB was worse in a lot of ways. Bear with me. ;-)
What HC did was provide an extremely limited palette of system features for you to play with. It was extensible, but only with difficulty, and there weren't many good extensions. (I used one that gave me access to the Mac serial port, and wrote one of my own that talked to a National Instruments data acquisition board). But I think the limitations were part of the secret of why it was so clean and easy to learn.
VB tried to be too much, by giving you all of the knobs and controls that let you create commercial-looking software. But you paid the price in complexity, and ultimately bloat. When VB-dot-net came along, I jumped ship and landed in the Python world.
And in the time between the introductions of HC and VB, computers got more complicated, with things like networking and databases that people wanted to mess with. And still more complicated between VB and VB-dot-net. Providing just the right degree of control for novices to write interesting programs, without exposing the ugly innards of the system, or deluging us with options, has always been the challenge of creating programming tools for the rest of us.
The rising complexity and expectations for modern computers is why it would be hard to resurrect HyperCard.
A non-obvious feature of HyperCard is that projects could be shared and distributed in source code form, meaning that there was no distinction between the development and user environments. It wasn't in text format, but a HC stack had a nearly 100% chance of working on someone else's computer without needing to worry about installers, dependencies, and so forth. And folks were encouraged to look at someone's code and learn from it.
There has always been a niche that blurs "use" and "programming," which is what is generically called "scientific programming." I work almost entirely within the Python ecosystem. I'm as happy, if not happier, than I ever was with HyperCard. A trick that I employ to deal with the complexity of the system is: Don't try to make it look and behave like real software."
Also, the environment that feels most like an environment for “not really programmers but sort of if I need to” is the Jupyter Notebook ecosystem which evolved out of IPython. It’s like a spreadsheet for telling a narrative.
On the Amiga we had a system called CanDo that was very similar to Hypercard in how it enabled end users to make multimedia applications. The interview below has some excellent insight into CanDo and the relationship it had with HyperCard.
http://www.rcfinch.com/Amiga/INOVAtronicsInterview.pdf
And I was reminded of these other application building tools, https://en.wikipedia.org/wiki/Amiga_programming_languages#Ap... the 3d construction kit kind of occupied the same place as minecraft for a lot of kids in the 90s.
*edit, his is fascinating https://en.wikipedia.org/wiki/Hyperland
I still use it on occasion to debug HID devices because it’s so fricken easy. Drag out the HID block, pick my device, drag the value I want to inspect onto a text render block. Done. Updates in real-time, essentially built an HID oscilloscope.
Update - old video of me using it to inspect a keyboard
I think the framework is even deprecated now.
https://andregarzia.com/2019/07/livecode-is-a-modern-day-hyp...
PS: I no longer work for LiveCode but I did back when I wrote that article.
This ground that HyperCard or Visual Basic 6 or Flash occupied has been ruthlessly razed and salted.
It is a pendulum swing between different members of the industry, some that prefer complexity as the source of their job security, and those that prefer simplicity and beauty (even if there are limitations).
Arguably NeXT IB and Objective C tried to straddle both worlds (and slid into complexity over time with iOS And MacOS)
Also See: Heroku vs Kubernetes
This would be have been fine, so long as these systems remained relatively simple, and were rebuilt in more heavyweight but scalable languages once they reached a certain level of complexity. But that isn't what happened. Instead, they just kept growing into twisted, unmaintainable monsters that organisations were completely reliant upon, but which were an absolute nightmare to maintain and extend.
As a result, the industry shifted to encouraging the use of "real" programming languages for everything, even the simplest systems, because the greater up-front costs were saved many times over by having a sane story for long-term maintenance and improvement.
I have seen an incredible number of businesses that run off of either Excel spreadsheets, or glomped together masses of Salesforce customizations. I'm not convinced that this is an improvement in matters.
I also think that there's just a lot of custom software that doesn't get built.
That makes a certain amount of sense; I know I've sworn at insane Excel spreadsheets that have lived far longer than they should have.
The thing I'd argue is that the vast majority of business tools are only useful for very few people for a very short period of time. Sometimes they are never useful. Doing those in a "real" language can have an ROI of centuries (or never), so just never get automated or tried. There's a very important place for cheap prototyping and if non-developers can do it that's even better.
why build software that empowers people to also build software easily, when you can charge thousand of €s in consultancy fees
It has one interesting point: complexity is our industry’s addiction and downfall, but blames the wrong person. it’s not Steve Jobs’ fault that customers want what they want.
The dream that we’d all be in a web based on HyperCard is no different from other the Squeak Smalltalk folks or LOGO fans etc. Elegant, beautiful interactive environments to help people learn computers, but never became mainstream problem solvers. It’s an old tale.
Otherwise it is mostly a “get off my lawn” rant.
(For those that don’t know about Squeak, Alan Kay believed in children’s programming so much they went to Disney - Disney! - to create Squeak, named after Mickey Mouse, as a next gen Smalltalk for kids.)
>The various HyperCard clones and HyperCard-influenced software lack HyperCard's radical simplicity and the resulting explorability. Explorability of the "master of all you survey" variety matters. All of the extra features in a more feature-rich system like SuperCard (or even VB) are not harmless. There is a fundamental difference, especially for a child, between a system which you can fully wrap your mind around and one with countless mystery knobs.
Says who?
>4. Everybody pushing Javascript, Python, Wx/Qt, Cocoa, and other abominations as "HyperCard replacements" simply does not remember being a child. And/or lacks a creative bone in his body. And/or is a malicious idiot.
Or the author might remember being a kid himself, but he doesn't know what is to be a kid in 2021. There are kids todays (even 8-12 year olds) who do more with Javascript, Python, Swift Playgrounds etc, than the best things ever done with HyperCard.
And the reason they don't use something like one of HyperCards successors, is not that it's 'too complicated', but that it doesn't really solve problems they have in 2021.
>But what he really sold us was a (fairly comfortable) train for the mind. A train which goes only where rails have been laid down
And yet Apple under Jobs and later, continued to ship AppleScript, shipped Swift Playground, and other such tools. And their subsidiary makes a powerful "build your own app" tool (FileMaker).
It's BS to present it as if HyperCard-made basically toy apps would be some kind of threat (or even just perceived as such) to Apple's bottom line or core products.
HyperCard alongside with other stuff was killed to re-focus Apple and save it. Apple was dying in near bankruptcy with HyperCard and Newton and everything - not only they weren't some big success, but not even the core offerings were much of success at the time either.
>Seems like many readers continue to miss the essential point, just as they did in 2011.
Or the point was bogus and the author insists on flogging a dead horse (or blowing a rusty trumpet)...
Reminds me of Apple's stance on mice with two or more buttons. To this day they still make them so it looks like it has one (or no) buttons.
> Either way, expect no HyperCard (or work-alikes) from Apple. But how about other vendors? What about open-source projects? Nothing there, either. Oh, there is no shortage of attempts. And all of them are failures for the same reason: they insist on being more capable, more complexity-laden than HyperCard. And thus, none of them can readily substitute for it.
That's it, not some conscious agenda by Jobs. A Mac will let you run anything you want, so why has nobody else made something like Hypercard? Why isn't there one for Linux or Windows or as a SPA web app?
Because of the second system effect and the general trend toward gratuitous unnecessary complexity at every level of the stack.
https://en.wikipedia.org/wiki/Second-system_effect
The other half of the answer is in my other reply. TL;DR: there are more programmers today than there were back then, but there are orders of magnitude more passive users who aren't "computer people" and just want a gadget that does a few specific things.
Walled gardens primarily service the latter, and do it acceptably well from their perspective. For the former there's Linux, FreeBSD, and commercial "real computer" OSes like MacOS and Windows that will let you run whatever you want with the proper incantations.
As time passed by I eventually ended up buying Delphi 3, just to find out that it was less intuitive than the Delphi 2 Shareware that I used excessively until then. Nowadays I even recommend non-technical people to take a look at Python when they consider writing anything more complex than an Excel formula. I'd be surprised if such tools ever become popular again.
> And if you think that XCode, Python, Processing, or the shit soup of
> HTML/Javascript/CSS are any kind of substitute for HyperCard, then
> read this post again. And if you continue to think so, then you might
> be an autistic typical software "engineer," and please don't waste
> your time commenting here. Sink back into the cube farm hellpit from whence you came.
Seems you ultimately need to go ad hominem to argue for this kind of software in 20xx.
"The reason for this is that HyperCard is an echo of a different world. One where the distinction between the "use" and "programming" of a computer has been weakened and awaits near-total erasure. A world where the personal computer is a mind-amplifier, and not merely an expensive video telephone. A world in which Apple's walled garden aesthetic has no place."
This is the antithesis of the UNIX way.
"The essence of the UNIX philosophy is not “make small utilities that can be fitted together with pipes” but to assume that at any moment, a user might decide to be a developer or a sysadmin and should have the tools to do that."
(unashamedly, -- me)
IMO, that's why it had to die ... and why it was not handed to its many user groups. Noble attempts to recreate its facility failed for lack of its ubiquity. One of the saddest stories in personal computing.
Eh. Making a calculator in LiveCode is a similar complexity to doing it in HyperCard:
https://subscription.packtpub.com/book/application_developme...
HyperCard and its successors are an accessible way to make very simple, fun little apps. You can use them to make more complex apps, but it's not significantly easier to use HyperCard than more conventional tools to do that. I think the reason HyperCard-like tools are not popular today is simply that there is little demand for such apps.
There is still no great tool for preschoolers to start programming. Scratch is great but limited by its web and flash roots.
I have very fond memories of getting balls to bounce on edges and sprites as a kid. RIP Hypercard
Imagine the look on our faces when my best friend and I tried this... and ended up getting the full source code to Myst in plain text. They didn’t even try to obscure it.
It really DeMystified (heheh) the act of professional development. They had used the exact same tools that I was proficient in to build something as meaningful and impactful as Myst, which literally changed the gaming world.
It's interesting to read here (http://myst.patchallel.com/myst_fl.html) how they used HyperCard as sort of just the "front end" to dispatch external commands and connect it all together. I just used Godot to make a game, my first that I've ever completed (including save/load functionality!). The interface and UI building tools, once you climb the gentle learning curve, are really quite incredible and the theming options gives you extensibility to define your aesthetic. If programming languages like Python or even Rust had this sort of quality WSYIWYG VB-style form editor, I think we could see a renaissance in desktop apps. I know at one time the Godot folks were considering Python as the scripting language for the engine.
Visual Basic is not dead, it's still in development (although in .NET form, which might have steeper learning curve). It was highly hyped in past too, but now it has only niche uses, and it's used not as "bicycle for mind", instead mostly for handling bureaucracy in large corporations.
I'm sure "calculator" example will be very similar in Visual Basic.
There are lots of no-code, low-code tools but they almost always fail and become discontinued quickly. Only spreadsheets thrive out of these.
There should be other reasons for that, not "corporations don't want users to program their computers".
"Jobs supposedly claimed that he intended his personal computer to be a "bicycle for the mind." But what he really sold us was a (fairly comfortable) train for the mind. A train which goes only where rails have been laid down, like any train, and can travel elsewhere only after rivers of sweat pour forth from armies of laborers. (Preferably in Cupertino.)"
So dramatic! Cmon now.
The sentiment at the bottom is what rings most true, you could fit the entire manual for hypercard in your head, and achieve proficiency much faster than many tools.
The author's answer to this question is totally wrong.
> Either way, expect no HyperCard (or work-alikes) from Apple. But how about other vendors? What about open-source projects? Nothing there, either. Oh, there is no shortage of attempts. And all of them are failures for the same reason: they insist on being more capable, more complexity-laden than HyperCard. And thus, none of them can readily substitute for it.
Really? Nobody ever had the intelligence and discipline to design a simple GUI builder in the history of computing since Hypercard?
No, the answer is that there are numerous simple GUI builders, including GUI builders for the web. But none of them are popular, due to the sweet spot of supply and demand that Hypercard hit.
When Hypercard launched, it came with every Mac, it was free, and there was nothing else like it available on the Mac. On the Mac, the alternative to Hypercard was to layout UI widgets in code, with no GUI builder at all, or eventually to pay $$$ for a professional-grade IDE like CodeWarrior. As an entry-level user with no budget, if you wanted a GUI builder for the Mac, you got Hypercard, or nothing. This created a community of Hypercard enthusiasts.
Furthermore, when Hypercard launched, Macs had a standard screen resolution. Every Mac sold had a screen resolution of 512x342 pixels, so you could know for sure how your cards would look on any Mac. Supporting resizable GUIs is one of the hardest things to do in any GUI builder. (How should the buttons layout when the screen gets very small, like a phone? Or very wide, like a 16:9 monitor?) Today, Xcode uses a sophisticated constraint solver / theorem prover to allow developers to build resizable UIs in a GUI; it works pretty well, I think, but it's never going to be as easy to learn as "drag the button onto the screen and it's going to look exactly like that everywhere."
The last issue is the real killer for modern Hypercard wannabes: it's a small step from a web GUI builder to raw HTML/CSS. You don't have to pay big bucks to have access to professional-grade HTML, CSS, and JavaScript. Sure, they're not that easy to learn, but you can teach a kid to write interactive web pages, no problem.
As a result, the demand for a simple GUI builder is lower than it was for Hypercard, and even when you do capture a user, they tend to outgrow your product, and there are a zillion competitors, so none of them can build a community with real traction.
There has been nothing stopping other companies from releasing HyperCard-style tools for the Mac. And many have. But they have (as far as I'm aware) not dominated nor flourished particularly well.
What may have seemed amazing to a few people -- including me; I loved HyperCard as a kid! -- was possibly simply not the most valuable use of time, especially for a company trying to dig itself out of the hole Apple was in during the late 90s.
As far as "use" and "programming" being kept separate in modern computers:
1) I don't think this is something a company even as powerful as Apple can control. Third parties would fill in the gap if masses of people were clamoring for a HyperCard-like experience. And arguably they have. You're reading this in a web browser, right?
2) I just don't buy that we're in some digital dystopia with an Iron Curtain between "users" and "programmers." What you can do with a computer just with "use" and not "programming" is just insane compared to the 1990s. "Non-technical" people who need to get something done can find a wide range of powerful tools to do the job. No one needs to make a calculator from scratch. No one needs to make most of the software tools they need in the day-to-day from scratch. And, again, there are plenty of available tools that allow for light scripting to give "non-programmers" even more control. And of course there are professional programmers who can do things with computers that lay people cannot. This would be true regardless of the existence of HyperCard.
For example, the musical instrument store where I worked in during high school used Hypercard to keep all their customer records and maintain an inventory of all their equipment. This was all based on custom "stacks" which were in turn lightly modified from included example stacks to add their specific business logic. (For example: the stacks would calculate rental fees and late rental charges instantly based on the store's arcane formulae. They would produce reports telling us who was late on rent and who was most likely to get really late. The stacks were constantly under development, which usually meant: we need a feature, let's pop the hood and add three lines of code.)
At the end of the day HC was just a single-machine database with an amazing programmable custom interface builder. This would have been obvious to me if I'd been older and understood these ideas, but I didn't realize how useful the combination was until many years later when I started building web apps. It occurred to me that what I was doing was basically making a much crummier version of Hypercard (albeit with a shared Internet-hosted database, which Hypercard did not have back then) at something like 100x the programming effort. I remember seeing that MS Access had some kind of interface builder, but it was a pile of hot garbage compared to Hypercard.
TL;DR if Hypercard had managed to stay the course and improve itself for that use-case I think Macs would have been vastly more useful to (at least small) businesses. Instead Macs went through a dark period where the nearly got killed by Windows, and were basically only saved by Jobs' attention to design plus Microsoft's reluctant benevolence.
None of them shipped with the OS. Maybe today it would make more sense to ship something like a Livecode educational version on Raspbian.
Geeks keep all sort of obscure things alive - GNU Emacs, OpenTTD, ReactOS. Either there are indeed Hypercard-like things out there, or this really is nothing more than nostalgia.
If you extend Hypercard to its logical conclusion you get either Flash or a browser running HTML locally. In any case you get a security nightmare, a lot of duplicated efforts, and the need to solve hard problems which didn't exist back then such as adapting UI to different screen sizes, accessibility, internationalization, publishing stacks on the web, etc.
Also, there were some commercial products developed with Hypercard back in the day... but these days you'd need a different development environment that supports things like versioning to entertain that possibility.
Could somebody explain me why?
I would argue that Swift Playgrounds also attempts to make software creation simple enough for anyone, but with a real programming language instead of a scripting language.
I still believe there are so much potential untapped in this HyperCard, no-code, or very little code Apps. But it seems it is similar to Nuclear Fusion it is always another 5 years away.
The argument isn’t super clear and it is not anything resembling an official or definitive answer to the headline.
Tl;dr: the author believes that hypercard was in the way of making the Mac a consumption device, because it allowed users to make their own things instead of buying it via the Apple store.
What happened is that computing became popular, vastly increasing the user base, and the majority of these new users didn't want to program any more than the average driver wants to work on the engine of their own car. They just wanted a computer to be a gadget they could use to do specific things: online interaction, spreadsheets, games, word processing, etc.
Is that bad? I don't do anything with my car but drive it (and rarely these days!). Am I missing out on the car experience?
Today's hobbyist computer market is larger than it was back in the good old days. We have an embarrassment of riches from cheap hardware (secondhand laptops that can run Linux are virtually free and there are dozens of <$50 Linux SBCs) to vast quantities of open source software available on aggregators like GitHub. There are vastly more creators than ever before. There are just orders of magnitude more passive casual users than those.
Suffice to say, I think many more people would make small changes that make their lives easier if if were easy and straightforward to do so as a user. Right now, it's not.
A car is a means of transportation, the fact that you can tweak the engine is tangential to its function, a computer is useful because, and not in spite, of its universality.
There isn't any logical way of using a computer that isn't programming, but ironically, it's often a mere afterthought in commercial products. To continue the obligatory car analogy, writing complex software in a full development environment is the equivalent of tweaking the engine. It's a job for professionals and I don't expect the average user to be able to do it. But writing a simple script for the system interpreter that wires premade components is more like changing your oil or changing a tire, it's really baffling that most people can't do it.
I wrote a blog post about how endemic this problem has become across the industry, Everything Old Isn't New Again (Yet) https://mimix.io/en/blog/everything-old