In this stream, I hope to wrap up this feature by getting constraints into the extension definitions, and then maybe move on to other features.
https://github.com/JasonBock/SaferAccessors/issues/4
#dotnet #csharp
In this stream, I hope to wrap up this feature by getting constraints into the extension definitions, and then maybe move on to other features.
https://github.com/JasonBock/SaferAccessors/issues/4
#dotnet #csharp

I haven’t done one of these posts for awhile, and the year is winding down fast. I personally have the Thanksgiving week, a big trip down under for the Yow Conference in Brisbane and Melbourne, and a fervent wish to take a lot more time off during the holidays than I have for years this year.
The big ticket items are major version releases of the major Critter Stack tools to add .NET 11 and drop .NET 9:
I don’t have a perfect timeline for when this will all be done, but we have alpha releases out for everything. We’re waiting a bit on some upstream dependencies like Npgsql 11 before we finish the official releases. I’m also abusing my poor MBP doing a lot of performance testing and optimization work that will continue for awhile.
For all of the tools, we’re trying to take advantage of new features in .NET 11 like the runtime asynchronous compilation to save on memory usage (which we’ve proven to benefit Wolverine at least) and some improvements for serialization. We’re investing much more this time in performance testing as we go than we were able to in the last round of major releases. We’re also doing a lot of work to try to lift duplicated code from Marten, Fisher, and Polecat into shared libraries as a way of easing support over time.
My big initiative for JasperFx right now is writing a new version of our internal CRM portal application to try to automate much more of JasperFx’s business. This is partially because I despise paperwork of all kinds and JasperFx has fortunately gained enough business that spreadsheets are no longer enough. I am also using this work to do more dogfooding of our greater “Event Modeling” story across the Critter Stack. We’ll put most of this code and work into a public repository and use this to rebuild a new set of tutorials on Event Modeling, Spec Driven Development, and using AI agents to scaffold Critter Stack applications.
Now, some bigger themes for new work:
Improvements to Wolverine’s Saga support and really its ability to support long running workflows all the way around. To be blunt, I’m looking to make Wolverine the absolute best server side platform for long running workflows out there, so we’re planning some improvements to the Saga support for diagnostics, error handling, compensation action support, more visualization and user interface or MCP management in CritterWatch, and even finally dipping our toes into a routing slip capability. I’m experimenting a little bit with an alternative syntax to define sagas through something like the Azure Durable Functions syntax that still functions as a Wolverine Saga behind the scenes. We will absolutely have an event sourced Saga capability that I think will pair very well with CritterWatch. I’m also going to experiment with using Wolverine’s virtual actor capability for long running tasks like file imports that don’t necessarily fit well into the existing messaging.
For the event stores, I think there’s an opportunity to expand our support for “cold storage” of event data to formal ways to “un-thaw” archived data on demand. A pair of JasperFx clients have now expressed interest in that.
Adding 2nd level caching to our event sourced command handlers. See this issue that’s been in our backlog quite awhile (that I would heavily consider dogfooding in CritterWatch). This will have to pair up with our global partitioning feature in Wolverine. More or less, the general idea is in some cases, we’ll basically have a very highly optimized architecture for event streaming within a cluster where operations are emitting events to persist in Marten or Polecat.
I guess I need to just come out and say that I’m somewhat interested in extending Wolverine into actor-based architectures. I think we have the foundation to do that already, especially after we had to harden our leadership election and agent assignment subsystem this year.
We need to break down and have an easy recipe for people to designate roles to different nodes in what’s otherwise the same Wolverine application. The need here is people who want only some nodes to run the transactional inbox/outbox agents or only some nodes to run messaging while maybe some nodes only handle HTTP traffic. Today you really need to do that with two logical Wolverine applications with isolated Wolverine node tracking storage.
I’m interested in adding formal support for the latest version of Quartz.Net in Wolverine and CritterWatch. Especially after Quartz.Net adopted Weasel for their own database schema management.
I don’t really know what to say about Stoat. I think the “AI Agent Wrangler” tool market is already way too crowded and it’s probably a fool’s game to play too much in that pool. The one thing that Stoat probably does earn its keep is managing and scheduling agent behavior and quality gates on a single box. Stoat might settle into just being a JasperFx internal tool, or it might grow into something that sits between the local work and newer AI planning tools like Linear.
Anyway, I’m thinking out loud here. I’m always interested in any feedback!
The 25th Anniversary of XBOX has given fans much to celebrate: the milestones, the memories, and a whole slate of fun news for our players. Â
We know that many of our longtime fans first learned about the original XBOX by reading about it in a magazine back in the day. For you, we created XBOX – The 25th Anniversary Magazine, a special publication designed not only to look back at 25 years of play, but also to celebrate the present and future of XBOX. We printed copies to share with community members at XBOX FanFest in Seattle this past week, and today, it’s available for all to read right here:Â
Protip: you can go full screen for easier reading by clicking the arrows in the lower right of the player.
The magazine explores games, hardware, and moments, past and present, told through the teams who are building them. You’ll revisit memories from your favorite franchises, learn some lore about XBOX’s storied history, and read new details about games that haven’t yet released; want to know more about Fable’s capital city of Bowerstone? Turn to page 38!Â
We hope you enjoy this decidedly analog celebration of the last quarter century and a first look at what’s ahead. Â XBOX’s story has always been written alongside our players. Thanks for reading, and for being part of what comes next.Â
The post XBOX 25th Anniversary Magazine: Explore 25 Years of Games, Stories, and Memories appeared first on XBOX Wire.