now we're getting a bunch of "if you don't like directives it's because you're not smart" posts ok if we're gonna go there then let's go there you babies think building software means doing create next app every 2 weeks on another dumbass side project you'll never finish and cramming 234 calls to 56 saas services but some people work on other types of software where their backend runs as a standalone service running on node or bun or something else there's a wide range of ways how this code gets compiled and run in production and they're all valid providing a library type feature that requires a compiler means it has to support every single configuration of this this is more to maintain, more opportunity for bugs, and undeniably more complexity so choosing to use this new workflows library is now a much heavier choice - across all our projects i don't have a single dependency that works this way effect manages to completely change js semantics and doesn't ask you to do this and to illustrate my point if i wanted to use this library today i can't because all our stuff runs on bun and they need to ship some bun plugin that calls rust transforms all so we can add a new kind of function coloring that's going to run into awkward apis for heavier work (which you haven't considered because remember you're a baby) i'm not saying this library is bad it still looks pretty good and a lot people will find value out of it but fuck off with the you're dumb if you don't like it shit