Author of TimeWarp.State https://xitter.cf/t.co/wQuANCMI0b npub1dh5md7ysepkc2eqne5cmy2prvxscgadchtjwyapjrq67guvnmgfsf7fqg4
Joined November 2009
- Tweets4.1K
- Following5.4K
- Followers1.7K
- Likes45.3K
Every repo of ours has a dev CLI. Same folder, same name, same shape. Clone it, type dev, and you're working.
Made a video walking through the one in TimeWarp.Nuru. It's all C#, built on Nuru, and the same tool serves me, CI and our agents.
The dev CLI from the video: github.com/TimeWarpEngineeri…
TimeWarp.Nuru, the CLI framework it's built on: github.com/TimeWarpEngineeri…
I am working on the 3 Vs. Verification, Validation and Visualization.
Verification: did we build it right?
Validation: did we build the right thing?
Visualization: can we see it?
With agents writing most of the code, these are the job now.
Running self-hosted GitHub Actions runners in wslc (WSL's new container tool) on Windows. Fresh --rm container per job, just-in-time registration, dotnet/sdk:10.0-noble base, non-root user, no Docker socket, not privileged. Private org repos only.
We are general contractors now not coders.
I spend my day writing the plan, handing work to agents, and checking what comes back. The skill isn't typing code anymore. It's knowing what good looks like.
A TimeWarp Nuru app, two routes, one call to EnableCompletion(). Tab completion in bash, zsh, fish and PowerShell, with no completion scripts written. Each shell asks the app, so new routes show up on the next Tab.
Every command I used is in the post, from the apt packages to the native AOT build, so you can reproduce it on your own machine. It also shows where each shell installs its script and the small differences between them.
thefreezeteam.com/posts/stev…
TimeWarp.Nuru 3.0 is out. Your .NET CLI is now a tool your AI agent can call. No MCP server. One package. 30 seconds, start to agent-callable:
3.0 moves contracts to TimeWarp.Mediator, swaps the MCP server for an in-context agent skill, and fixed 22 issues an agent-run code review found before release. Migration guide and repo are in the reply below.
Repo: github.com/TimeWarpEngineeri…
Release post: thefreezeteam.com/posts/stev…
Steven T. Cramer #dotnet retweeted
🤖 Blazor goes agentic! 🚀
New Blazor AI components help you build chat UIs, stream responses, manage conversations, and create AI-powered experiences using familiar .NET patterns. 🧠⚡
Build smarter apps with less boilerplate.
📖 Read: msft.it/6014altpn
ALT A promotional image featuring a purple background and white text. It states, 'Build Agentic UI with the new Blazor AI components' and includes icons for .NET, a generic symbol, and a stylized '@'.
Steven T. Cramer #dotnet retweeted
Aspire 13.6 features, day 3
The Aspire dashboard goes Native AOT! 🤯
🚀 66% shorter page-visible startup
⚡ More responsive UI
📦 No installed .NET runtime required
🛠️ Built on .NET 11 for the latest features and Blazor fixes
Try it today. @aspiredotdev 13.6 is out now!
ALT Median page-visible startup graph
Every Rust reply when someone suggests C# is now:
“Why would I choose C# when even @stephentoub chose Rust?”
Whatever reasoning comes after that line, the line still wins. Making the case for .NET just got harder.
That hurts. Toub’s write-ups are the ones we quote to defend the choice. This feels like et tu, Brute.
First Anders takes the TypeScript compiler to Go. Now Toub takes the Copilot runtime to Rust. These don’t happen in a vacuum. An ecosystem was built, people bet their careers on it, and the person we pointed to as the “why C#” priest just picked a different church.
@shanselman this doesn’t stay in a blog post. The ecosystem you helped grow is the one we have to defend in comment sections tomorrow, and the citation we used just walked off the stage.
If Microsoft is porting, it's mission critical infrastructure to non-.NET languages, do I need to be worried about building my clients mission critical infrastructure on .NET?