Tag: comparison

In ASP.NET Core 11, return Results<T1, TN> with TypedResults for minimal APIs and ActionResult<T> for controllers. Treat bare IResult and bare IActionResult as escape hatches: they compile for any response but describe nothing to OpenAPI, so you pay for them in hand-written ProducesResponseType attributes.

Use CreateBuilder for a normal app, CreateSlimBuilder when you publish trimmed or Native AOT behind a TLS proxy, and CreateEmptyBuilder only when you want to register every service yourself. Here is the feature matrix and the gotchas that force the call.

On EF Core 11, default to complex types for value objects and drop to owned entities only when you need a separate table or a collection mapped to its own rows.

Output caching is the right default for almost every server-side app in ASP.NET Core 11. Response caching only wins when your goal is to steer browser and proxy caches through HTTP headers. Here is the decision, with a feature matrix and the gotchas that force the call.

On EF Core 11, default to TPH for almost every hierarchy, reach for TPC only when you mostly query one leaf type and a benchmark proves it wins, and use TPT only when an external constraint forces you to.

Sequential for pipelines, concurrent for fan-out, group chat for moderated rounds, handoff for routing, magentic for open-ended planning. The C# builders and how to choose.

Both produce the same SQL. Reach for named filters only when you need to disable one predicate independently; a single combined filter is simpler for one concern in EF Core 11.

For a long list, never use shrinkWrap. Use Expanded when the list is the only scrollable, and slivers (CustomScrollView) when it shares a scroll with other sections. Here is why, with a build-count benchmark.

Both let one agent spawn isolated workers from a Markdown file, but Claude Code nests five levels deep with per-agent tool allowlists and worktree isolation, while Cursor keeps it to two levels with a single readonly switch and reads Claude's format for free. Pick by where your agents run, not by brand.

Build a skill to change how Claude works, a subagent to protect your context window, and an MCP server to reach a system Claude cannot otherwise touch. They solve three different problems, not one. Here is the decision, the mechanics, and the config for each.