itch.io app timeline 2016
👋 This page was last updated ~9 years ago. Just so you know.
I’ve been working on the itch.io desktop app for about a year now, so I thought I’d make a quick recap:
At the time of this writing, the app has been downloaded about 460K times (including updates). Not counting the back-end, the app and its various components are made up of around 100K lines of code (mostly javascript and golang), most of which is open-source.
You’d think after all that I’d go take a nap or something, but the Winter 2016 season is far from over and I couldn’t be more excited about what is still to come.
In the meantime, be sure to check out:
- https://itch.io/app - install and keep your itch.io games up-to-date!
- https://itch.io/docs/butler - our command-line uploader, patcher, and more.
These are both part of itch.io refinery, a customizable toolset for first releases & playtests.
If you have any questions, we’re always listening at mailto:hello@itch.io!
I’d like to thank my itch.io colleagues, all our testers, translators, and the game developers who adopted the system early and have shown incredible kindness and understanding, taking the “stress” out of “stress testing”!
Talk to you in 2017 with hopefully a lot more bullet points :)
Did you know I also make videos? Check them out on PeerTube and also YouTube!
Here's another article just for you:
A dynamic linker murder mystery
I write a ton of articles about rust. And in those articles, the main focus is about writing Rust code that compiles. Once it compiles, well, we’re basically in the clear! Especially if it compiles to a single executable, that’s made up entirely of Rust code.
That works great for short tutorials, or one-off explorations.
Unfortunately, “in the real world”, our code often has to share the stage with other code. And Rust is great at that. Compiling Go code to a static library, for example, is relatively finnicky. It insists on being built with GCC (and no other compiler), and linked with GNU ld (and no other linker).