Hacker News new | past | comments | ask | show | jobs | submit login

The reason I switched to Lambda was to handle bursts. Occasionally some teacher would have a classroom open LilyBin, and my one server couldn't compile 30 scores at once. Lambda made it easy to handle.

Hacklily is great! Obviously doing fine with the HN burst! I may just point people to yours at some point.




This sounds like a really interesting problem. What kind of transformation is taking place during compilation, datatype wise, like are you rendering audio serverside?

I wonder for a classroom setting, if many people compile similar scores, if there's any opportunity to say "the first half of all these scores are the same, compile it once and concatenate it with the unique pieces"...caching composition...I'm sure I'll play with it someday.


For Hacklily, it turns out that the audio is rendered clientside via https://github.com/hacklily/hackmidi

Caching sheet music rendering is a hard problem. For example, a note later in the score can affect the spacing of notes before it.


If you have considered using a queue, what were your reasoning to prefer lambdas?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: