Emoji Generator/Picker/Designer (early stages but you can play around with it)
- since it's procedural, you can transition between expressions, and there can be way more possibilities than if each emoji were hand-designed.
Input Control library for games (idea stage)
- modular UI, and network effects (centralized development effort and familiarity of the UI between games that use it)
Ooplie - program in English (early stages)
- eventually leveraging the npm ecosystem a lot, hopefully ((or another ecosystem)),
altho I haven't thought of the best way to create interoperability without too much boilerplalte
- it might be that everything in the ooplie ecosystem is a wrapper,
which means a lot of abstraction, a lot of surface area for bugs
(or just friction, generally - things missing from the libraries that are in the original modules,
potential for bugs, and performance)
node-ahk - desktop automation for Node.js (early stages),
a platform that already has tons and tons of packages
("basically all the functionality" you could need, packaged so you can easily include it in your program),
and you can use various languages to script. (Python, Ruby, Go, you name it!)
The main thing that sucks about AutoHotKey is the language.
The language and the limited ecosystem.
- user interface design concepts that can be applied to many (if not all) creative programs,
as well as the prospect of sharing code for "tools" (brushes etc.) between different types of programs
(which you could also call "tools", that's why I'm putting quotes around "tools"), among other things,
and just generally trying to accomplish more with less, filling the roles of many programs with a small core perhaps
More projects (unaffiliated)
- provides abstractions for different types and configurations of virtual filesystems in browser.
You can use the Node.js APIs, so lots of code could potentially work with it without change.
- provides abstractions for interfacing with different desktop environments (including Electron) with a single API