2 ms·
Hypertalk (the language of HyperCard) had a lot of syntactic sugar, but was pretty easy to get started with even with almost no programming background. For exa
by jandrese 7y ago
Hypertalk (the language of HyperCard) had a lot of syntactic sugar, but was pretty easy to get started with even with almost no programming background.
For example, a very simple button might have a script that looks like:
on mouseUp
ask "What is your name?"
put it into card field "Name"
end mouseUp
You could get pretty far by reading scripts and trying things out in Hypercard.
I also tend to think that the idea of network aware Hypercard sounds super cool, but would have been a security nightmare. Hypercard wasn't written in an era of adversarial coding, it would have been knocked over 10 different ways every day by hackers. Code and content were heavily mixed together and there was no permission model beyond preventing people from editing your stacks by accident. Every stack or even card you loaded would be downloading and executing code.
- DonHopkins 7y agoHyperCard inspired Arthur van Hoff to develop a network aware version of HyperCard in PostScript for James Gosling's networked-PostScript-based NeWS Window System. It was originally called "GoodNeWS", then called "HyperNeWS", then finally released as a product called "HyperLook", which I worked on with Arthur and used to port SimCity to X11/NeWS on SunOS/Solaris. https://en.wikipedia.org/wiki/Arthur_van_Hoff https://en.wikipedia.org/wiki/Arthur_van_Hoff Arthur later went on to Sun, wrote the Java compiler in Java, developed the AWT user interface toolkit, then formed Marimba with Kim Polesi and Jonathan Payne and others from the original Java team, where they developed Castanet and Bongo. https://www.wired.com/1996/11/es-marimba/ https://www.wired.com/1996/11/es-marimba/ >1996-11-01: Tuning in to Marimba. Kim Polese wants you to upgrade your HTML-based browser to a more interactive, more TV-like, Java-based "tuner" by the name of Castanet. >Marimba's first product, scheduled to be announced in early October, is the punnily named Castanet, which aims to push Java toward its full potential. Java was created to deliver interactive content over distributed networks, and its much-hyped arrival last year promised to completely change the way information and entertainment are delivered electronically. The first popular Java programs have been based on HTML - for example, the Java applets that lend some animation to boring Web pages. But Java doesn't need the Web to fly. It was designed to communicate over any kind of decentralized system. [...] Marimba developed Bongo, a Java-based gui toolkit / user interface editor / graphical environment, inspired by HyperCard (and HyperLook), which they used to develop and distribute interactive user interfaces over Castanet. https://people.apache.org/~jim/NewArchitect/webtech/1997/10/note/index.html https://people.apache.org/~jim/NewArchitect/webtech/1997/10/... >Feel the Beat with Marimba's Bongo, By Chris Baron >In 1996, four programmers from the original Java-development team left Sun to form Marimba and produce industrial-strength Java-development tools for user interface and application administration. Bongo, one of Marimba's two shipping products, allows developers to create either a Java-application interface or a standalone Java-based application called a "presentation." A Bongo presentation resembles a HyperCard stack -- it allows developers to quickly create an application with a sophisticated user interface, but without the tedious programming of directly coding in Java or C/C++. Bongo's nonprogramming, visual approach makes it ideal for producing simple applications that don't involve a lot of processing, such as product demonstrations, user-interface prototypes, and training applications. Bongo is fully integrated with Castanet, Marimba's other product, a technology for remotely installing and updating Java applications. Bongo was unique at the time in that it actually let you edit and dynamically compile scripts for event handlers and "live code" at run-time (in contrast with other tools that required you to recompile and re-run the application to make changes to the user interface), which was made possible by calling back to the Java compiler (which Arthur had written before at Sun, so he knew how to integrate the compiler at runtime like a modern IDE would do). Without the ability to dynamically edit scripts at runtime (easy with an interpreted language like HyperTalk or PostScript or JavaScript, but trickier for a compiled language like Java), you can't hold a candle to HyperCard, because interactive scripting is an essential feature. Danny Goodman, who wrote the book on HyperCard, also wrote a book about Bongo. Arthur later founded Flipboard and JauntVR, and now works at Apple. https://www.amazon.com/Official-Marimba-Guide-Bongo-Goodman/dp/1575212544 https://www.amazon.com/Official-Marimba-Guide-Bongo-Goodman/... I've written lots more about HyperLook, NeWS and SimCity: https://medium.com/@donhopkins/hyperlook-nee-hypernews-nee-goodnews-99f411e58ce4 https://medium.com/@donhopkins/hyperlook-nee-hypernews-nee-g... https://news.ycombinator.com/item?id=19837817 https://news.ycombinator.com/item?id=19837817 https://news.ycombinator.com/item?id=18314265 https://news.ycombinator.com/item?id=18314265 https://news.ycombinator.com/item?id=20182294 https://news.ycombinator.com/item?id=20182294 https://news.ycombinator.com/item?id=19007885 https://news.ycombinator.com/item?id=19007885
- paulrpotts 7y ago>You could get pretty far by reading scripts and trying things out in Hypercard. I think that's true - but my experience was that it was a good language for beginners, but didn't "scale" well as you started working on more complex programs. The English-like syntax could get in the way as soon as you started to assemble more complex expressions, and you'd be left hunting for the right syntax as if you were playing an old Infocom game. It gave the impression that the parser was more accommodating and sophisticated than it really was, when really it had a rigid syntax like most other programming languages. And because most of the documentation was aimed at beginners, it was hard to find clear answers about _exactly_ what the syntax had to look like when assembling those more complex expressions. It has been a long time since I was writing HyperTalk, but I remember being very frustrated that I couldn't find a formal language spec (in BNF or a bubble diagram or something) the way I could for languages like Pascal. Still, it really should get a lot of credit for encouraging a lot of beginners to write code and build quite sophisticated little databases complete with all kinds of animations and visual effects that would have been monstrously difficult to code from scratch in C or Pascal. I should also remember that as a programmer and Computer Science student, _I was not the real target audience_ for the language design.