Introduction
In the mid‑2020s, a quiet rebellion in software design has been gaining momentum. Developers, artists, and educators are rediscovering the joy of direct, tactile interaction with computers—a philosophy that powered the legendary HyperCard in the late 1980s and early 1990s. HyperCard, created by Bill Atkinson at Apple, allowed anyone to build interactive “stacks” of cards without writing traditional code. It turned the Macintosh into a creative laboratory for non‑programmers. Now, in 2026, a new platform called Decker is resurrecting that spirit while embracing the ethos of “vibe coding”—an approach where the focus is on mood, exploration, and rapid iteration rather than strict syntax and architecture.
Decker is not a clone of HyperCard; it is a thoughtful re‑imagining that runs on modern browsers and operating systems, yet retains the minimalist charm of classic Mac OS interfaces. It uses a simple markup language called “Lil” and offers a visual canvas where you can draw, type, and link cards together. This article explores what makes Decker unique, how it builds on HyperCard’s legacy, and why it perfectly embodies the vibe coding movement. Whether you are a seasoned developer or someone who just wants to make something fun, Decker invites you to play.
The Legacy of HyperCard
HyperCard, released in 1987, was one of the first widely‑used hypermedia systems. It let users create stacks of virtual cards, each containing text, graphics, and buttons. Behind each button you could write simple scripts in a language called HyperTalk, which read almost like English. “On mouseUp” was a common trigger. This ease of use made HyperCard a tool for prototyping, education, and even commercial software—Myst, the iconic puzzle‑adventure game, was prototyped on HyperCard.
However, HyperCard was tightly coupled to the classic Mac OS. With the transition to Mac OS X and the abandonment of 68k/PPC native code, HyperCard became a relic. Apple officially discontinued it in 2004. The creative void it left was immense. Several attempts have been made to revive its ideas—for instance, SuperCard, Revolution (now LiveCode), and more recently, tools like Twine for interactive fiction. None achieved the same cultural impact—until Decker started gaining traction around 2024.
Enter Decker: A Modern Revival
Decker was created by Kavi, a developer and designer who wanted to capture the “hypercard feel” without the baggage of a proprietary runtime. Decker runs entirely in a web browser or as a standalone application (written in C and using SDL). It produces standalone HTML files that can be shared or viewed offline. The key philosophy behind Decker is: minimalism, instant feedback, and no build steps.
Core Features
| Feature | Description |
|---|---|
| Card‑based model | Each deck is a series of cards, each with a full‑screen canvas. |
| Markup language (Lil) | Lil is a tiny, easy‑to‑learn language for adding logic. It runs on a simple stack machine. |
| Built‑in drawing tools | You can draw shapes, lines, and add text directly on cards. |
| Hyperlinks between cards | Clickable zones can jump to other cards or run Lil scripts. |
| Export to standalone HTML | One command produces a single HTML file with all assets embedded. |
| Retro aesthetic | Default fonts, window chrome, and color palette mimic classic Mac OS 7/8. |
Decker does not require you to install anything beyond a modern web browser. You can start building a deck within minutes. The source code is available on GitHub, which allows anyone to fork and modify the platform itself. This openness has led to a small but vibrant community creating decks—from interactive storytelling to educational quizzes to tiny games.
Decker and the Vibe Coding Phenomenon
“Vibe coding” is a term that emerged around 2024 to describe a style of programming where the emotional tone, aesthetic, and exploratory process are prioritised over correctness, performance, or scalability. It echoes the “computation as material” idea of early computing pioneers like Alan Kay and Douglas Engelbart. Decker is a natural fit for vibe coding because it removes the friction of setting up a development environment, parsing error messages, or worrying about cross‑platform compatibility.
- Low barrier to entry: You don’t need to be a programmer. You can create a deck by simply drawing and linking cards. If you want to add interactivity, Lil syntax is designed to be readable:
when “button” is clicked, go to card 3. - Immediate visual feedback: Every change is reflected instantly. There is no compilation, no reload. This encourages tinkering.
- Remix culture: Many decks are shared under Creative Commons licenses. You can download a deck, modify it, and republish it—much like the early HyperCard stacks were freely exchanged on bulletin boards and diskettes.
- Nostalgia with a purpose: The retro look is not just a gimmick; it reduces cognitive overhead by stripping away modern interface clutter. Users can focus on content and logic.
A concrete example: At the 2025 “Vibe Coding Jam” (an online event), participants created over 40 decks in 48 hours. One standout was a “dream log” deck where users could click on different dream symbols to reveal interpretations. The creator had no prior coding experience and said, “I just drew some clouds, added text, and linked cards. It felt like making a scrapbook that comes alive.”
Practical Example: Building a Simple Interactive Stack
Let’s walk through a miniature project—a choose‑your‑own‑adventure story about a robot exploring a cave. This demonstrates Decker’s core workflow.
- Start a new deck. In the Decker editor, you see an empty card. Draw a simple cave entrance using the rectangle and line tools.
- Add a choice button. Use the “button” tool to create a clickable hotspot that says “Enter the cave.”
- Link to a new card. Click the button and select “Link to new card.” Decker creates a fresh canvas. Draw the interior of the cave (maybe some stalactites and a glowing crystal).
- Add another choice. On the interior card, place two buttons: “Touch the crystal” and “Follow the tunnel.”
- Write a tiny Lil script. When the player touches the crystal, you might want to show a message. Go to the card’s script panel and type:
when "crystal" is clicked say "The crystal glows warmly!" ok - Export. Click “Export as HTML.” Now you have a standalone file that runs in any browser. Share it with friends.
This whole process takes less than ten minutes. No frameworks, no npm installs, no server. That’s the vibe coding promise Decker delivers.
How Decker Compares to Other Platforms
To understand Decker’s place, we can compare it with similar tools available in 2026.
| Platform | Paradigm | Target Audience | Modern Updates | Code Required? |
|---|---|---|---|---|
| Decker | Card stacks + Lil | Hobbyists, educators, nostalgists | Active, open source | Minimal (optional) |
| Twine | Hypertext game engine | Interactive fiction writers | Active | No (but supports JavaScript) |
| Scratch | Block‑based programming | Children, beginners | Active | No |
| LiveCode | Scripted (English-like) | Professional devs | Commercial, paid | Yes |
| Glitch | Web app editor with remix | Web developers | Active | Yes (HTML/CSS/JS) |
Decker’s niche is the intersection of retro aesthetics, hypertext, and minimal programming. It is less powerful than LiveCode for building full‑fledged apps, but far easier to pick up. It is more visual than Twine because you can draw graphics directly on cards. And it appeals to adults who find Scratch too childish but want a similar lack of friction.
Where Decker Falls Short
- Limited programming model: Lil is not Turing‑complete in a conventional sense—you cannot do complex data structures or networking. It’s designed for simple event handling and state changes.
- No collaboration features: Unlike Glitch or Google Docs, there is no real‑time co‑editing. (However, you can share exported HTML files.)
- Small community: As of 2026, the community around Decker is still niche. Forums and tutorial collections are growing, but you won’t find Stack Overflow answers for every question.
Why Decker Matters in 2026
In a world dominated by massive frameworks, cloud APIs, and AI code generation, Decker stands as a counterpoint. It reminds us that software can be small, personal, and fun. The “vibe coding” movement is partly a reaction against the industrialisation of programming—the sense that every project needs a CI/CD pipeline, containerisation, and a microservices architecture. Decker offers a safe space to fail, to experiment, to make something that is not optimized for scale but for expression.
Educators have started using Decker to teach basic logic and storytelling. Because the results are immediately playable, students stay motivated. Artists use it to create interactive art portfolios without hiring a developer. And many just enjoy the nostalgic feel of a classic Mac interface—the chunky fonts, the absence of rounded corners, the familiar “window shade” effect.
Conclusion
Decker is more than a HyperCard clone; it is a vehicle for a philosophy of computing that values human expression over technical sophistication. By combining the simplicity of a card stack, the charm of old‑school Mac design, and the accessibility of a modern browser, it has carved out a unique spot in the 2026 software landscape. Whether you call it “vibe coding,” “creative computing,” or just “playing around,” Decker invites you to make something that exists purely for the joy of making.
If you want to dive deeper, the best way is to open the Decker editor in your browser and draw your first card. Or explore the community decks on Itch.io and GitHub. The future of software may be vast neural networks, but the present can still contain a small, delightful card stack built by one person in an afternoon.
(Decker's source code is freely available on GitHub, where you can explore it, fork it, and contribute. For context, ASI Biont supports connecting to GitHub via API — more at asibiont.com/courses.)
Comments