Live data from Hacker News

Show HN: Trigger.dev V2 – a Temporal alternative for TypeScript devs

trigger.dev

41–44 of 44 posts

Re: Show HN: Trigger.dev V2 – a Temporal alternative for TypeScript devs

#41
post #2

Coming to Next.js from Laravel, being able to hand things off to a long running worker is one of the things I missed the most. We're currently handling this with a non-ideal solution and will definitely check Trigger.dev out when you launch that feature.

May I ask what made you to switch from Laravel to Next.js?

Would like to know this as well. I switched from my last company’s WordPress app over to our Laravel side of things (with Vue/Inertia on the front end) and I really liked it. I’ve heard of Next.js here and there but seeing in the context of “switched from Laravel” I’m very curious.

Re: Show HN: Trigger.dev V2 – a Temporal alternative for TypeScript devs

#42
post #19

How does it compare to inngest.com?

Chiming in as a founder of Inngest. We released our TS SDK a year ago so had quite a head start in this area. The approach in their V2 release makes them more similar to us, though there are still some large differences, including the fundamental architecture, queueing technology, scale, etc. Some differences you'll notice as a developer: - Concurrency and parallelism. We allow you to run steps in parallel, configure…

Just want to say, as a somewhat new HN user (l would end up here occasionally via search or Reddit, which I jumped ship after the API changes so HN is my home now), it’s really great to see you and the founder (iirc) of windmill both here in the comments.

Re: Show HN: Trigger.dev V2 – a Temporal alternative for TypeScript devs

#43

The marketing landing page looks very similar to Vercel's homepage. https://i.imgur.com/o5Cdldv.png

This has been a trend for at least past 3 years after Tailwind made it easy to add gradients to and

If anything they have a cool slider/tabs for different actions.

Re: Show HN: Trigger.dev V2 – a Temporal alternative for TypeScript devs

#44

My initial thought when opening your website was that this was a job queue, like BullMQ. Not a "link things together like IFTT/Zapier/N8N but in code" platform. I don't think I'd use "Background Jobs framework" to describe what you're building, as that term has very different associations. Am I right in saying this is like BullMQ, except with integrations? If so, I'd focus more on the integration part of your marketi…

That's really interesting. What associations do you have with "Background Jobs framework"? Quite a lot of our customers are using us instead of Temporal. Not for linking stuff together use cases.

Just a background job queue library basically. Maybe with a fancy dashboard. That was my first impression.
Post reply on HN