Comment by doctorpangloss

Comment by doctorpangloss 13 hours ago

I like Trigger but it's a lot of complexity...

> use cases like compute-heavy tasks such as generating videos using AI (Icon.com), real-time computer use (Scrapybara), AI enrichment pipelines (Pallet, Centralize), and vibe coding tools (Hero UI, Magic Patterns, Capy.ai)

Okay, but aren't these websites using Trigger to schedule remarketing slop? Like adding you to Slack, sending you an email on day 1, sending you an email on day 7, etc... How exactly is it being used to power applications? You know what the difference is.

eallam 12 hours ago

That's actually how we started back during YC W23 as a "Zapier for developers" but we pivoted to "async workflows" later in 2023 and have since been used less like Zapier and more like the core part of an apps infra/backend, which has taken off with AI applications building AI workflows and agents, including those examples you quoted there.

Reply View 0 replies

alexdanilowicz 10 hours ago

co-founder of Magic Patterns here, saw were were mentioned, figured I'd chime in:

We don't use Trigger for marketing at all and I actually never thought of it for that use case.

We're an AI design tool - prompt to create an interactive mockup - and we use Trigger to take screenshots of designs to provide a preview image. Taking a screenshot sounds easy, but it's not because Puppeteer constantly hits OOM errors. So you need a high-end machine, and so it can get expensive. We originally were using a homegrown solution, a microservice, but it would constantly crash (even though were paying $$$$$ for it).

Trigger spinning up jobs was perfect and we migrated in a day and now I never think about it.

Reply View 1 reply

jan_g 7 hours ago

Can you expand a bit on this use case? Why would Puppeteer constantly crash on your own high end machine, but not on Trigger's infra? Puppeteer doesn't care where it runs, so it would be nice to understand how Trigger's infra works around this problem.

Reply View | 0 replies