Profile avatar
goodman.dev
Curious mind. Creator of https://plnkr.co. Tech lead for extensibility at Auth0 (OKTA). I will never stop experimenting.
63 posts 61 followers 119 following
Regular Contributor
Active Commenter
Posts 17 Comments 33

Sending unsolicited AI-generated email to the address scraped from my GitHub profile is not a growth hack, it's in violation of the CAN-SPAM act.

submitted 14 days ago • 0 comments

Some critical projects like @typescriptlang.org don't (or can't) follow SemVer. They suggest users pin versions in package.json. But what if npm package versions could explicitly *declare* their compatibility range. Clients could further constrain ranges for upon opt in. Best of both worlds.

submitted 36 days ago • 0 comments

I've seen folks looking to use AsyncLocalStorage as a way to propagate identity across async boundaries in server logic. That seems very scary to me because AFAIK it relies on 3rd party libs opting into AsyncResource or risking confusion in some edge cases. WDYT?

submitted 44 days ago • 0 comments

WinterTC is here 🎉 TC55 is a new Ecma Technical Committee for Web-interoperable Server Runtimes, originating from the existing W3C WinterCG group. This means the group is now able to publish standards, with the first effort being the Minimum Common API.

submitted 49 days ago • 0 comments

What are some useful pattern you’d expect to work across bundlers? We’re collecting a list here: github.com/tc39/js-outr...

submitted 51 days ago • 1 comment

@zachleat.com fascinating interview on @syntax.fm. Very inspiring. It sounds like many of the product velocity benefits of federation could also accrue on the backend. Do you have thoughts / observations? Worthwhile pursuit?

submitted 72 days ago • 1 comment

This seems like a fascinating innovation in load balancing but I feel like I didn't get a full picture from the talk: 1. Do the use the latency of the Probes or some aggregate of the Queries as predictors? 2. What if Queries are very heterogenous? 3. How do they derive predicted latency for RIF(n)?

submitted 73 days ago • 0 comments

Here's my aspirational vision for a modelcontextprotocol.io (MCP) project. I'm pretty excited by the potential but the scope is _huge_. If you're unfamiliar with the MCP, it tries to standardize a protocol for clients like Claude, Zed editor, etc. to get extensible super-powers. WDYT?

submitted 77 days ago • 0 comments

We are hosting an MCP hackathon in SF (December 10th) and NYC (December 11th) and giving away $30,000 In Anthropic API credits. Come join us! x.com/alexalbert__.... 🧵for more info

submitted 84 days ago • 4 comments

Huge deal! It happened. I hope this will pull back the ESM CJS partition that crept in. Bravo @joyeecheung.bsky.social and collaborators!

submitted 86 days ago • 0 comments

I bet OCI images (docker images) are a pretty perfect distribution format for MCP servers. As containers, we can abstract away dependencies while also isolating the host system as much as we want. And they should *just work* as stdio servers with the `-i` flag. Anyone already working on this?

submitted 88 days ago • 0 comments

I bet OCI images (docker images) are a pretty perfect distribution format for MCP servers. As containers, we can abstract away dependencies while also isolating the host system as much as we want. And they should *just work* as stdio servers with the `-i` flag. Anyone already working on this?

submitted 88 days ago • 0 comments

Here is a fun one for you all: contrary to popular belief, in Node.js promises (async/await) would not yield to the event loop. So, if you want the event loop to process I/O in between a long chain of async functions that actually aren’t doing I/O, you would need to add a setImmediate in between.

submitted 91 days ago • 4 comments

I think @anthropic.com's Model Context Protocol is fascinating. I've been re-implementing the stdio and sse protocols to understand the inner workings and am at the MVP stage. I'm exposing a custom weather tool that always responds with `"sunny with a chance of meatballs"` 🤣. Claude is onto me.

submitted 91 days ago • 1 comment

Once upon a time, Agile was agile.

submitted 93 days ago • 0 comments

TIL that browser fetch doesn't allow duck-typed AbortSignal instances or Proxy instances that wrap real signals. Seems like a bit of a bummer for performant, interoperable AbortSignal tooling. Is this by design?

submitted 93 days ago • 0 comments

The very need for this makes me think it is evidence or a larger disconnect: package.json tries to encode metadata for three very distinct and sometimes mutually exclusive use-cases: 1. Developing the library / service / app 2. Consuming the library 3. Running the service / app

submitted 94 days ago • 1 comment