Recent submissions

Comment · 3 years ago
I’m the post author, and I use this same polyfill. I even install it with the same NPM download method I wrote about.
Comment · 4 years ago
Yes, pretty much. It’s definitely cool that so many folks here have left positive feedback, but ultimately I don’t have the same bandwidth and motivation that I had when I started this project. Whenever those return, I’ll return to it. Until then, I’m just planning to chew on the core idea and take in everyone’s suggestions.
Comment · 4 years ago
Comment · 4 years ago
Thanks a bunch! I wonder which gear brands you had in mind when commenting. Teenage Engineering had a big influence on how I make music, and I like to think some of their charm shines through in Typebeat.
Comment · 4 years ago
Hi HN! I’ve been working on Typebeat for a year and a half, and I decided yesterday to make the code public. There’s also a website where you can download the macOS build and try an online demo:

https://typebeat.kofi.sexy

The project was initially conceived as “vim for music”. All of Typebeat is controlled by the 30 main character keys on the computer keyboard. The result is a workflow that’s a little tricky to learn but fast to use once mastered. (So I suppose I nailed the vim experience in that regard.) If you’d like to see how I use it at top speed, you can check out this 2-minute jam I made recently:

https://youtube.com/watch?v=RT0qUB4gbas

Comment · 6 years ago
I'd highly recommend "The Beam Book" by Erik Stenman: https://blog.stenmans.org/theBeamBook/

A few years ago, I spent my free time building a Haskell BEAM codegen library, and that was by far the best resource I found. I noted some other projects that helped me understand things here: https://github.com/kofigumbs/codec-beam#acknowledgements

Comment · 6 years ago
Fair enough, updated.
Comment · 6 years ago
Author here—my understanding of the GPL matches that in the sibling comment. "GPL never says you cannot sell your software. It just says you have to provide source with it and you cannot prevent others from redistributing the source."

If I'm incorrectly co-opting some open source nomenclature, I'd love if someone could let me know. As I said in the issue linked above, I do need to update the purchase website to bring that language more inline with what's on GitHub.

Comment · 6 years ago
Author here—that's pretty embarrassing, and I'm not sure how I messed that up. I do recall having to retake the Activity Monitor screenshots between drafts, so I'm going to blame my mistake on that. Adding an editorial note now!

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton