Hypercard was great as a drag and drop "app" builder. Apple actually coded up iWeb a few years later, for which Hypercard could have been an excellent foundation. 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
Why Hypercard had to die (2011)
121–130 of 171 posts
Re: Why Hypercard had to die (2011)
#122I don't buy this argument. 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 ou…
None of them shipped with the OS. Maybe today it would make more sense to ship something like a Livecode educational version on Raspbian.
Re: Why Hypercard had to die (2011)
#123Re: Why Hypercard had to die (2011)
#124As 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.
Re: Why Hypercard had to die (2011)
#125Myst was originally built using HyperCard, which I always thought was rather clever
Which lead to a pretty magical moment for me as a kid. Turns out it’s trivial to write a HyperCard program that opens another HyperCard stack and extract its source code. 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 us…
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.
Re: Why Hypercard had to die (2011)
#126HyperCard broke all the UI conventions of the Mac. You couldn’t use it to create native look and feel Mac apps.
You absolutely could (I did a couple enterprise-y projects with HyperCard during that era), but it required dedication and discipline.
Re: Why Hypercard had to die (2011)
#127The walled garden rant is anachronistic. HyperCard died because Apple stopped major work it. Circa 1987! There was no HyperCard team to put out a new version when Jobs returned in 1997, and a dying Apple couldn’t justify building one from scratch. It’s that simple. (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…
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.
Re: Why Hypercard had to die (2011)
#128I think people give Hypercard (and Flash) too much credit. Its easy to make UIs if you use absolute resolution and position. You can make apps with about the same effort today using a lot of modern WYSIWYG tools but its the scaling layouts that are so tedious.
Re: Why Hypercard had to die (2011)
#129Re: Why Hypercard had to die (2011)
#130Honestly, people need to get over HyperCard. 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.
i wouldn't call the web elegent or powerful today either