Image 1 — A look back at the past
Image 2 — A look back at the past
Image 3 — A look back at the past
Image 4 — A look back at the past
▲ 326 r/dotnet

A look back at the past

I noticed a discussion in the comments yesterday about the Professional Active Server Pages 2.0 book from Wrox, which back in the day was one of the only sources of information us oldies had to work with as a reference for classic ASP. Even one of the authors chimed in and is still active in this sub (Brian Francis).

I’ve kept my copy. I also have a number of books in my bookshelves that were invaluable back in the day and some of them I’ve kept for posterity even though they are worthless from a tech perspective now.

Hopefully they bring back nice memories for some of you too.

u/desnowcat — 4 days ago
▲ 12 r/Temporal+1 crossposts

Temporal Nexus .NET SDK preview

As part of my role in the Temporal Constellation Program I sometimes get insights into the development pipeline at Temporal to review features before they hit GA. I was recently asked to review the Nexus support in the Temporal .NET SDK by the Temporal engineering team.

For larger organizations who operate lots of different Temporal namespaces and want to communicate between them, or teams running microservices, Nexus brings an alternative communications approach with the resilience Temporal brings to the table. If you are frequently turning to Azure Event Grid inter-domain communication and you don’t need granular RBAC, then Nexus could alleviate your infrastructure complexity.

Blog post walks you through it, but you can also just clone the linked repo and try it out yourself.

If you want to see how I use Squad from Brady Gaster with Aspire and Playwright to speed up this demo development using the Aspire team’s agentic loops, you can watch it self testing the UI.

Feel free to follow me on LinkedIn for more frequent content.

Note: Posted on the weekend under the permitted self promotion rules of this subreddit.

rebecca-powell.com
u/desnowcat — 3 months ago

Guarantees for Sol Terra and Luna cost multipliers?

I’m on a grandfathered GitHub Copilot Pro annual subscription (legacy). As such, the new models are excluded to me. Personally I think this is a bit of a dark pattern that GitHub chose to do this to people who took out a yearly subscription, but that’s a side point.

My annual account that cost $100 runs until December 2026. That’s $8.33 per month plus I’m spending about $30-$35 on premium requests on top monthly.

The newer Pro+ billed monthly is $39 per month so I’m pretty much at break even if I switched. What’s not clear are the following:

- if I switch to Pro+ is the remainder of the Pro annual legacy credited to my account?
- does this affect the rate limits I’m seeing on Pro? I hit these frequently.
- most importantly how long is the 1x cost multipliers going to remain stable for Sol, Luna and Terra? This weighs heavily on the decision. GPT 5.4 is currently a 6x multipler and when on Auto for the 10% discount I’m seeing this model picked frequently.

Are there others facing a similar decision, currently locked out from newer models?

Is there anything else I’ve overlooked here? Should I just use an Open AI API key with GitHub Copilot CLI (BYOK) until the end of the year? Any other alternatives that compare with these newer models?

I think the hardest challenge here is that I don’t trust GitHub to keep the 1x multiplier on these new models. They’ve already screwed me over on the yearly Pro plan.

Thoughts?

https://docs.github.com/en/copilot/reference/copilot-billing/request-based-billing-legacy/model-multipliers-for-annual-plans

u/desnowcat — 3 months ago