Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Make any TypeScript function durable

useworkflow.dev

Post reply on HN
Print view View original

21–30 of 89 posts

Re: Make any TypeScript function durable

#21

Post by javcasas »

evilduck wrote: post #17
javcasas wrote: post #9

Earlier quoted context omitted.

My bad, this is open telemetry stuff to check the status of your servers, not for the vendor to slurp as much data from you as possible.

This is Open Telemetry functions you're referencing. Being able to trace, profile and debug your own code that's executing in a highly distributed environment is a pretty useful thing. This isn't (necessarily) user behavior telemetry. At least understand what you're looking at before getting the ick.

That's fair. I'm too accustomed to seeing the other type of telemetry shoved in all over the place.

Re: Make any TypeScript function durable

#22

Post by Etheryte »

MrJohz wrote: post #14
Etheryte wrote: post #2

Of all the syntax options they could've gone with, they settled on what I would say is arguably the worst. If you want a one-liner, decorators are widely used across different languages and Typescript supports them as well.

Decorators don't work for functions, unfortunately, so wouldn't work in this case. You'd need to add a bunch of class boilerplate to make it work. JavaScript didn't have a lot of great options for this kind of statically-declared metaprogramming, which is why the "use X"; syntax has become so popular in various spaces. It's definitely not my favourite approach, but I don't think there's any clear "best" solution here…

Since this magic string requires a preprocessor step anyway, there's no reason they couldn't make it a decorator that works on functions. I don't see the problem?

Re: Make any TypeScript function durable

#23

Post by lloydatkinson »

zzixp wrote: post #19

This is actually pretty cool. We have a similar custom library at Xbox that's used extensively across all of our services. I do wish that there was some kind of self-hostable World implementation at launch. If other PAAS providers jump onto this, I could see this sticking around.

Azures Durable Task Framework or something else? I guess there’s nothing public on it, which is a shame because it sounds interesting

Re: Make any TypeScript function durable

#24

Post by oompydoompy74 »

javcasas wrote: post #3
Etheryte wrote: post #2

Of all the syntax options they could've gone with, they settled on what I would say is arguably the worst. If you want a one-liner, decorators are widely used across different languages and Typescript supports them as well.

My bad, this is open telemetry stuff to check the status of your servers, not for vendors to extract as much data as they can from you. > I'm trying to find how they implemented the "use workflow" thing, and before I could find it I already found https://github.com/vercel/workflow/blob/main/packages/core/s... > Telemetry is part of the core. > Yuck.

It’s apparently an swc compiler plugin.

Re: Make any TypeScript function durable

#28

Post by TimTheTinker »

I'd rather be explicit about what's going on at each step. That way idempotent functions can be handled differently, retry limits can be applied, and no separate preprocessor is required.

    export async function welcome(userId: string) {
      const user = await retry(() => getUser(userId));
      const { subject, body } = await retry(() => generateEmail({
        name: user.name, plan: user.plan
      }));
      const { status } = await retry(() => sendEmail({
        to: user.email,
        subject,
        body,
      }), 2);
      return { status, subject, body };
    }

Re: Make any TypeScript function durable

#29

Post by c-hendricks »

drawfloat wrote: post #10

Use client and use server aren’t great, but the fact they had to be declared at the top of a file was at least clear. Starting to scatter magic strings throughout a code base feels like a real step back.

There's nothing about "use server" that requires it to be at the top of the file though, it can go in function bodies and you have a typed RPC method.

I think "use client" is the only one that has to go at the top of a file.

Re: Make any TypeScript function durable

#30

Post by ngruhn »

Etheryte wrote: post #22
MrJohz wrote: post #14

Earlier quoted context omitted.

Decorators don't work for functions, unfortunately, so wouldn't work in this case. You'd need to add a bunch of class boilerplate to make it work. JavaScript didn't have a lot of great options for this kind of statically-declared metaprogramming, which is why the "use X"; syntax has become so popular in various spaces. It's definitely not my favourite approach, but I don't think there's any clear "best" solution here…

Since this magic string requires a preprocessor step anyway, there's no reason they couldn't make it a decorator that works on functions. I don't see the problem?

But then it's not valid TypeScript anymore. So all the other tooling breaks: syntax highlighting, LSP, Linter, ...
Post reply on HN