Comment by reverseblade2
Comment by reverseblade2 5 days ago
Yes, most of the project evolved because of potential customers who later disappeared. Someone shows up and says, “Hey, we’ll pay you if you provide this feature,” so I implement it… and then they vanish
The API came about the same way. Currently, there’s just one active API user: a company from Sri Lanka that built a Unity WASM interface on top of it.
I coded the algorithm completely from scratch, with no external inspiration and fun fact, it’s written in F# using functional programming. There are a lot of immutable lists floating around. Honestly, I probably wouldn’t have been able to write it without functional programming (even though it’s notoriously slow for this kind of problem). The immutability allowed me to focus on individual parts of the app without worrying about side effects.
That said, how it works and how fast it works still feels like magic to me, just like any meta-heuristic algorithm applied to combinatorial problems.
And thanks for the feedback! I knew the Blog link was broken after I redid the landing page, but I didn’t notice the duplicated API Response Structure section. I’ll definitely fix that. Though part of me thinks, “Should I really bother?”
Also, thanks for catching the audio/subtitle issues. I was aware of both, but I figured it wouldn’t make much difference at this stage. Maybe that attitude explains my low traction… who knows? Either way, I appreciate you taking the time to point these out!
Cool! And yes I'm a little surprised that you used a functional programming language for the implementation, I'll have to have a look at F#.