I switched from Cursor to Neovim and at first I hated Neovim’s poor AI ghost text. Now I kind of like the break from heavy AI when I write code.
The vast vast majority of my code is written by Claude Code, so I don’t write much. But when I do it’s like an exercise in warding off programming atrophy
> You shouldn't be blocking the main event loop for 30 seconds! The main event loop is not intended to be used for heavy processing.
This article is talking about an SDK that runs in users' apps. Users can run whatever code they want, so the SDK has to find a way to keep sending the outgoing heartbeats
We'll release an Upstash Workflows adapter soon! StepKit is ultimately just an in-code API that lets you define workflows in a backend agnostic way. We want you to define workflows that can run in Upstash, Inngest, Cloudflare... really anywhere!
Vercel Workflow Kit takes a very different approach. Lack of step IDs (which makes them worse at handling code changes), compilation step, more opinionated about backends ("worlds", as they call them). Vercel Workflow Kit has magic that admittedly makes it a little easier to get started, but that magic causes problems when you want a mature product.
Cloudflare Workflows are actually complementary to StepKit! We'll soon release an adapter that lets you define StepKit workflows that run as Cloudflare Workflows. We have a POC in `packages/cloudflare` in our repo
Inngest engineer here! For a little extra context, the `@stepkit/core` package is basically just an API for defining a workflow. There isn't much to it because we don't want to be overly opinionated on backend implementations!
The `@stepkit/sdk-tools` package is a set of tools for building your own StepKit SDK. The vast vast majority of stuff in there is optional, but highly valuable if you want to avoid reinventing the wheel when building your own SDK.
We’re still really early in the AR/VR space. Hardware is bulky and expensive but that’ll change over time. Eventually we’ll have lightweight, high-fidelity, reasonably-priced hardware and AR/VR usage will be common
> ... someone would immediately fork the project and do it for free
He said he's tried to find others to maintain the project and no one will help. Dunno why it'd be any different if there was a fork.
> ... not expect every installer to give you a dollar.
He isn't asking for every installer to pay. He's asking for enough financial support to work on core-js full-time, which seems reasonable given how depended-on the library is.