Steven T. Cramer #dotnet

@thdxr So if I'm on windows with WSL where is this server running?

one pattern we could do is the first time you run opencode it forks into the background as a server then every other time you launch it or use the webapp or desktop app they all use that one instance so everything is synced i'm worried this feels unexpected to people though

@codemullins Yes, this is what we want and a WASI first operating system.

what if we built a new browser that focused on .NET and WASM first

@DevLeaderCa github.com/TimeWarpEngine…

@DevLeaderCa I am working on Timewarp.Jaribu a runfile based testing framework. I am more focused on integration. Also use TimeWarp.Fixie convention on top of Fixie.

What's your approach to unit testing in .NET? Any preferred frameworks or tools?

@gholdridge @jfversluis 100%

@jfversluis 10. Been upgrading annually since 2022, 3-6 months after release. Decided it was less work than upgrading from 2-3 versions behind. And get all the benefits asap. Practically no breaking changes these days.

What's the oldest .NET version still running in your production? No judgment. Just curious how far back some of us are holding the line.

@MithunShanbhag @jfversluis Yes this is the way. ;)

@jfversluis .NET 10

@donna_boschen @Rainmaker1973 I live in Thailand and have pineapple smoothie almost every morning. The peel I would be careful there but the core blended up is fine eat the whole thing they are great. Mix in some avocado and banana great. I can't prove any health benefits but I know they taste great :)

@Rainmaker1973 I eat a lot of pineapple.. it has gotten thru some bad flares with my rheumatoid arthritis .. autoimmune disorder… not like regular arthritis.. AND! I also take bromelain capsules .. on an empty stomach so it’ll digest any fibrous dead tissue floating around.. helps pain a lot

The secret behind why everyone’s boiling pineapples

@marcsh @LukeParkerDev what kind of tools? Have link?

@LukeParkerDev Im (VERY) slowly trying to build up a set of C# LLMish tools since we need more Right now its literally mostly a half finished OpenAI server shim, and calling out to python via PythonNet Is anyone putting together something where we can all yell at each other about style?

okay help me out guys

I'm down. Lets go.

@XFreeze Just wondering can we use the sub with OpenCode also?

xAI just dropped a massive new offer for SuperGrok Heavy plan 67% off for 6 months - now $99/month instead of $300/month Includes: • Near-unlimited usage • 16x AI agents in Expert Mode • Early access to new features • Dedicated support • Access to Grok Build Early Beta • xAI’s most powerful reasoning tools And this is just the beginning There are a lot of new Grok models and features coming very soon xAI is moving insanely fast right now Subscribe while the offer is still available

Great will give it a go tomorrow.

Agents in .NET just leveled up. Part 3 breaks down how to build autonomous, tool‑using, memory‑aware agents with sessions, context providers, and multi‑agent workflows. If you’re building real AI systems, this one’s a must‑read. 👉 ift.tt/4zw3hvp

@aarnott I try to keep updated with latest. It's better as that is the actual version my libs are tested against. The dotnet choice is a trade off to avoid bloat.

Why is it that when NuGet people have dependency X, which has a dependency on dependency Y, and Y comes out with a new version, that people expect X to ship a whole new version just to update the Y version it depends on, when as a consumer of X you can totally update Y yourself.

the last 10% is the hard part or something... anyway the flicker is gone. opencode desktop is about to get scary fast. idle cpu lower, less time on reflow, blah blah yep its fast

@mjovanovictech I'm not sold yet, the `with` operator skipping validation is one big one. And once you don't use them then you have inconsistency. I switched everything to them once and then switched them all back.

I resisted primary constructors in C# for a while. The syntax looked nice, but one thing bothered me: Primary constructor parameters are captured as mutable variables. They are not `readonly` fields. That felt like a trade-off I didn’t want to make. But after using them across several projects, I changed my mind. For DI service classes, the boilerplate savings are hard to ignore. Instead of this: - private readonly fields - constructor parameters - field assignments - then the actual code You declare the dependencies once and use them directly. The class becomes shorter. The intent is easier to see. And for typical ASPNET Core services, that mutable capture pitfall is usually manageable. I still don’t use primary constructors everywhere. I stick with traditional constructors when I need: - complex validation - multiple overloads - stronger immutability guarantees - too many dependencies But for DI service classes? I’m sold. I wrote a full breakdown of why I switched, where I use them, and the one pitfall you need to understand: milanjovanovic.tech/blog/why-i-swi…

@Calhighlander @LiuInTheShadows "Legit gov" is pretty much an oxymoron. I think we have seen worldwide at this point that "gov" is by those that can hold power, only. Sadly.

@LiuInTheShadows Best Bet, Pull every thing out of CCP China, have products made elese where. Return our Embasy to TiPia, Tiwan. Recoinize once agin TIWAN. It Simple. CCP was never a Legit Gov. It dose not play fair. We the world needs to totaly cut them off til they learn to behave.

🚨 stop scrolling.. do you understand what this CEO delegation actually means in dollar terms.. because most people are only thinking about the handshakes.. these 12 companies have a combined market cap above $10 trillion.. every single CEO on that plane needs something specific from Beijing.. Musk needs China to keep building Teslas without a 100% tariff eating the margin.. Huang needs chip export licenses that let Nvidia sell into the world's largest AI market.. Cook needs Apple's $70 billion China supply chain to stay intact.. Fink and Solomon need Chinese financial markets to open so Wall Street can actually operate there.. Boeing needs China to unfreeze $50 billion in plane orders sitting in a backlog since 2019.. and here's what nobody wants to say out loud.. every one of those CEOs is on that plane because they already calculated that staying home costs more than the flight.. the combined revenue exposure to China across those 12 companies is over $300 billion a year.. that's not a diplomatic trip.. that's a $300 billion ask dressed up as a state visit.. if Xi says yes to even half of it.. the trade war framework changes overnight.. if Xi says no.. 12 of the most powerful CEOs in the world flew to Beijing for a photo op.. and markets will price that answer in real time. if you're not following me you're finding out about this 48 hours late from someone who read my post..

Speaking of hubris, do you know something SpaceX, Google, Anthropic and more don't? You may, I don't claim to have studied it enough to offer an informed opinion. Maybe it is a bad idea but at least people won't complain about a data center being put in their neighborhood. I wonder what the hourly rate is for the guy who has to do the on-premise support :) 555.

@WatcherGuru Space data centers solve one problem and create ten new ones. Who is fixing the servers when they break? What happens when a solar flare hits? This is peak tech hubris. Just because Elon can launch it does not mean it is a good idea

JUST IN: Google $GOOGL in talks with Elon Musk's SpaceX to launch data centers in space.

@nickchapsas I have cared about it since it was Project Tye. Hopefully will get to do more soon.

Man, does anyone care about Aspire outside of Microsoft? It feels like the AI hype has overshadowed one of the coolest projects that launched in a very unfortunate time, solving a problem everyone already had a solution for

@Vmrs_13 @elorwelliano I don't understand what authoritarian capitalism is. To me that is an oxymoron. So I assume our definitions differ.

@elorwelliano La derecha económica asocia todo lo malo al "socialismo"="dictadura", pero no etiqueta igual al capitalismo autoritario que es peor

NUEVA YORK: CRÓNICA DE UNA MUERTE ANUNCIADA 🚨🇺🇸 Goldman Sachs huye de Nueva York y deja en pánico al alcalde socialista Mamdani. El alcalde de Nueva York enfrenta un duro golpe tras confirmarse que Goldman Sachs, uno de los gigantes históricos de Wall Street, está obligando a cientos de sus gerentes y empleados a elegir entre mudarse a Dallas, Texas, o Salt Lake City, o abandonar la empresa por completo, debido a los insostenibles costos operativos provocados por los aumentos de impuestos y regulaciones impulsados por su administración socialista. El éxodo masivo de la icónica firma hacia estados más amigables con los negocios marca el inicio de un colapso económico anunciado en la Gran Manzana.

@kristijan_kralj Please give me a link to your GitHub with an enterprise example of your recommended way.

The hidden cost of "enterprise" .NET architecture: Debugging hell. I've spent 13+ years in .NET codebases, and I keep seeing the same pattern: Teams add layers upon layers, to solve the problems they don't have. IUserService calls IUserRepository. IUserRepository wraps IUserDataAccess. IUserDataAccess calls IUserQueryBuilder. IUserQueryBuilder finally hits the database. I've seen a lot of classes having one-line methods whose sole purpose was to call the next layer and that's it. But to change one validation rule, you step through 5 layers. To fix a bug, you open 7 files. The justification is always the same: "What if we need to swap out Entity Framework?" "What if we switch databases?" "What if we need multiple implementations?" What if this, what if that. The reality: Those "what ifs" don't come to life in 99% of cases. I haven't worked on a project where we had to swap the ORM. But I've seen dozens of developers waste hours navigating through abstraction mazes. This happens with both new and experienced developers. New developers asking on Slack all the time: "Where to put this new piece of code?" But senior developers are too busy to answer that message. Why? Because they are debugging through the code that has more layers than a wedding cake. The end result? You spend more time navigating than building. Good abstractions hide complexity. Bad abstractions ARE the complexity. And most enterprise .NET apps? Way too much of the second kind.