3 ms·
That's what I thought, and I figured this would be a good way for startups to save time that would otherwise be spent finding, deploying and maintaining job sch
by shpxnvz 16y ago
That's what I thought, and I figured this would be a good way for startups to save time that would otherwise be spent finding, deploying and maintaining job scheduling infrastructure.
But, given the lack of interest I wonder if it's just not something most startups think they need?
- johns 16y agoIt's more that they don't need it yet. I think you should run with it for a little while and see where it goes. If you can add more value than just cron via REST, you might have something. I don't know what that value is.
- shpxnvz 16y agoI don't know what that value is. Me either, which is of course part of what I was hoping to get some insight about from the discussion here. I've some ideas about what I would have been happy to have found when I was starting projects, e.g. a simple hosted API for user lifecycle management, but little evidence so far to support viability as paid services. Well, I suppose I'll just have to launch them and find out, then.