Picked the open source model over the API, now I'm paying for it in time

Last month I had to decide between hooking up an API that costs 2 cents per call or running a local open source model on my own rig. I went with the open source one because I'm cheap and hate monthly bills. Setup took 3 hours, then I spent another evening fighting with dependencies, and the output quality is noticeably worse at making sense of my messy voice notes. Has anyone else made this trade and actually gone back to the paid API after wasting a weekend?

2 comments

2 Comments

taraw163d agoMost Upvoted

This whole thing reminds me of the pattern where people pick the free option to save money, then blow way more time and energy than the money was even worth. Like when someone buys a cheap lawnmower at a garage sale, spends three weekends fixing it, and then goes out and buys the new one anyway. Or when people download a free PDF editor and end up reformatting the whole document by hand because the text layers are garbage. The hidden cost is always your time, and time is the one thing you can't get back. So yeah, going back to the paid API sounds like the same move. You paid 2 cents per call to skip the headache, and those 3 hours you burned could have been spent on your actual project.

oliver_mitchell1d ago

Is burning three hours really that bad when you learned something out of it though?

-1