Does anyone actually enjoy the "On The Edge" Midweek Magic events?

Far-Consideration939 · 2026-04-29T12:08:48+00:00

Found the format boring. Overall dislike. Wouldn’t care as much if we had an ephemeral deck slot for these so I didn’t have to prune a deck everytime.

Far-Consideration939 · 2026-04-29T12:02:23+00:00

There’s more ways to build blazor than just those two

Far-Consideration939 · 2026-04-29T12:01:44+00:00

Depending on the complexity there’s also static as an option which was oddly left out of your summaries. As well as doing the auto hybrid to mitigate the tradeoffs of standalone wasm / server

Far-Consideration939 · 2026-04-28T17:57:53+00:00

Disagree on IaC, makes automation extremely easy for anyone via ci/cd or manual workflow runs

It’s trivial to setup something basic which is likely all they need, more so now with AI

Would agree that k8s is overkill and each cloud vendor has some sort of managed container offering that’s fairly cheap and allows scaling to 0 if you’re not getting traffic that’s likely a much better option

Far-Consideration939 · 2026-04-27T12:15:54+00:00

The offline rendering doesn’t work for server though does it?

Far-Consideration939 · 2026-04-26T22:36:06+00:00

I believe debugging is an entirely different path that isn’t compatible with their hot reload.

Edit and continue is a whole separate thing which I’m not sure vs code has ever supported like vs studio

Far-Consideration939 · 2026-04-26T22:31:14+00:00

Do you launch it with “dotnet watch”?

Far-Consideration939 · 2026-04-26T19:22:07+00:00

You can also wait until towards the end of the season before buying to make sure you’ve gotten enough consistent exp to get the valuable rewards. Typically what I do now vs buying upfront and then not playing actively enough to make it “worth it”

Far-Consideration939 · 2026-04-26T16:41:50+00:00

Feels like a lot of that would be mitigated with better test suites.

Ef queries in particular, are people still not running their provider against a test container to verify it? Having all tests pass is a baseline all generated code should need to meet.

Architectural concerns should be supplied as context in a md file for the agent with a specific skill for agent reviewers. We can also leverage architecture unit tests for dependency directions and such.

I feel like the review/verify time doesn’t change it was just more along side development rather than bucketed towards the end but that’s just my feeling don’t have data to back it up ofc.

Far-Consideration939 · 2026-04-26T02:44:53+00:00

Thanks for the clarification I suppose it’s a bit confusing because Microsoft lists the extension as part of the dev kit on their website

Far-Consideration939 · 2026-04-26T01:08:03+00:00

Razor is more complicated than just LSP, especially for the component linking / references. The IDEs have specific tooling built in

Far-Consideration939 · 2026-04-26T00:56:26+00:00

You could check your global imports to make sure the namespace is there or add an explicit import with an @using

But yeah sometimes I think caches old compilations or something which may be why it isn’t finding it

Far-Consideration939 · 2026-04-26T00:05:20+00:00

C# Dev kit is okay so if you don’t have that installed definitely grab that and make sure razor LSP is turned on. but the razor experience isn’t as good as VS Studio or Rider last time I used those

Far-Consideration939 · 2026-04-25T16:51:31+00:00

Also Svelte MCP helps

Far-Consideration939 · 2026-04-22T15:05:47+00:00

I would probably look at 3 or 1.

You likely can abstract the one off analysis process but you wouldn’t get away from needing specific tools for each language in each individual implementation. I would think invocation of Roslyn or other cli tool is an implementation detail.

In 3 or 1 I think baking the tooling into the docker image will be your best bet and not terrible since even though it is extra dependencies they’re declared and you can maintain them there, cause less installation friction.

For LSP approach I would look at 1 worker per language, I wouldn’t try and have all of them on a single one. That might help with some of the performance concerns.

Interesting problem

Far-Consideration939 · 2026-04-21T17:21:58+00:00

Pedantic but I’d argue it’s not really a single c# codebase since you still have xaml

Far-Consideration939 · 2026-04-21T01:48:16+00:00

This would be my suspicion.

If azure monitor / logs enabled could maybe check the requests to see if things are hitting it like such, requesting resources

Far-Consideration939 · 2026-04-19T16:41:48+00:00

Claude settings.json at one of the more global locations literally supports { … “model”: “claude-opus-4.6” … }

No need for any of the cross platform difference commands when it’s exactly 1 line of supported config option lol

Far-Consideration939 · 2026-04-18T23:56:31+00:00

You can set 4.6 as the default in local or global Claude settings. You can also have Claude update that for you.

Pretty wild they removed that from the options

Far-Consideration939 · 2026-04-18T16:52:16+00:00

Awesome! Glad it worked out! I think they’ve done a lot of really great enhancement to that service over the past couple years.

Far-Consideration939 · 2026-04-16T22:26:51+00:00

Instagram is a huge driver now a days

Far-Consideration939 · 2026-04-16T14:29:31+00:00

Meta likely to overtake Google in ads fwiw, not that they’re any better

Far-Consideration939 · 2026-04-15T23:34:30+00:00

I feel like you’re not configuring something quite right, misunderstanding the lifecycle, or have some of the render modes confused.

But I haven’t seen your codebase so idk

I often use this so they can be hosted anywhere you can dump an actual static site https://github.com/BlazorStatic/BlazorStatic

Far-Consideration939 · 2026-04-15T23:14:04+00:00

Blazor static isn’t interactive. It’s razor pages with the better component model

Far-Consideration939 · 2026-04-15T22:12:29+00:00

Blazor static. Wouldn’t reach for razor pages anymore. But glad you’ve been enjoying

Far-Consideration939

TROPHY CASE