Nu and Io on GitHub
Things have been quiet around here lately as we prepare for the launch. We’re doing a lot of work on the backend to ensure we will be stable and swift…
Things have been quiet around here lately as we prepare for the launch. We’re doing a lot of work on the backend to ensure we will be stable and swift moving forward. More on this soon.
In the meantime, you can now enjoy two of my favorite languages right here on GitHub: Nu and Io.
Here’s a description of Nu straight from programming.nu:
Nu is an interpreted object-oriented language. Its syntax comes from Lisp, but Nu is semantically closer to Ruby than Lisp. Nu is implemented in Objective-C and is designed to take full advantange of the Objective-C runtime and the many mature class libraries written in Objective-C. Nu code can fully interoperate with code written in Objective-C; messages can be sent to and from objects with no concern for whether those messages are implemented in Objective-C or Nu.
Follow Tim Burks or check out his Nu repo to watch for updates.
Io is also great, and incredibly dynamic. Really, it puts Ruby to shame in the metaproggin’ department. From iolanguage.com:
Io is a small, prototype-based programming language. The ideas in Io are mostly inspired by Smalltalk (all values are objects, all messages are dynamic), Self (prototype-based), NewtonScript (differential inheritance), Act1 (actors and futures for concurrency), LISP (code is a runtime inspectable/modifiable tree) and Lua (small, embeddable).
Follow Steve Dekorte or check out his Io repo to watch it progress.
Written by
Related posts

From MCP to multi-agents: The top 10 new open source AI projects on GitHub right now and why they matter
Get insights on the latest trends from GitHub experts while catching up on these exciting new projects.

Racing into 2025 with new GitHub Innovation Graph data
Discover the latest trends and insights on public software development activity on GitHub with the quarterly release of data for the Innovation Graph, updated through December 2024.

GitHub Availability Report: March 2025
In March, we experienced one incident that resulted in degraded performance across GitHub services.