Blog

From the garden

  • The release where I found out what I had shipped

    A second registry I announced that did not work, three ways your own code could take the process down, and the two improvements my benchmark was too small to see.

    green-teareleaseperformancereliability

  • Trust is a feature, and I had shipped it as a TODO

    What it took to make green-tea operable: an observability contract, shutdown that actually lets go, a routing difference between runtimes I did not know I had — and two people who contributed to a project with no stars.

    green-teastoryobservabilitycontributors

  • Green Tea 26.8.0-beta.0: the router stops guessing

    Safe constrained routes, strict paths, complete HEAD and OPTIONS semantics, four runtime targets, and the limits we are deliberately leaving visible.

    green-teareleaseroutingsecurity

  • I benchmarked green-tea honestly. The network humbled it.

    Every framework claims it's faster. I put green-tea on two real machines with a real network between them and watched most of that story evaporate — plus the O(n²) I found in my own code while I was there.

    green-teabenchmarkshonesty

  • Why I rebuilt my framework from scratch

    I built a decorator framework on Express and Inversify. Then the foundation kept moving under me. So I rebuilt the idea from zero — as a graph.

    green-teastoryarchitecture