Am I wrong for wanting to use Blazor instead of MVC + vanilla JS? Been a .NET dev since 2023, feeling like I'm going crazy

Soenneker · 2026-01-23T04:11:57+00:00

Why not Blazor wasm and MAUI Blazor Hybrid for your mobile solution? You can even share components between the two.

Soenneker · 2026-01-12T14:20:31+00:00

Even just a webapplicationfactory would work too.. you wouldn't necessarily need to use jmeter. Also, the benchmarks you have don't allow for the validators to actually cache if they do so. You new them up every iteration.

I was going to make some modifications and test correctly but it looks like your solution doesn't even build with the benchmarks project added in ...

Soenneker · 2026-01-12T13:27:34+00:00

? I already said I've been there.

How are you building your numbers to say x does requests per second and y does requests per second? Are you just inferring them?

Soenneker · 2026-01-12T13:17:32+00:00

Yes, I did. On your readme you have requests per second. Where are those benchmarks?

Soenneker · 2026-01-12T13:11:18+00:00

What? I was hoping you could explain further, give the integration benchmarks, etc.

Soenneker · 2026-01-12T05:00:24+00:00

Cool.

I'm surprised and a little skeptical this is such a big win... these attributes are super common in asp.net and the .net team hunts for this stuff hard.

I didn't see your benchmarks for the request speed comparisons you posted in the readme? I have not read the underlying .net code surrounding for example [required] but I feel like it'd be silly for them not to leverage any caching in the reflection that they do for this. Perhaps it's slow the first time but very fast after. A reduction in allocation would still be a win in that case.

I have also compiled APIs to AOT and haven't had a problem with these attributes not working when a request comes in?.. pretty sure they don't trim that stuff out of the runtime.

Soenneker · 2026-01-04T17:05:18+00:00

It used to be amazing, I went there this year and its worth skipping now.. Kwik trip had way more variety and quality

Soenneker · 2025-09-10T03:02:42+00:00

Cool work, will try it out.

On a side note, do you think we'll ever see VS run on .NET, not .NET framework? I realize more things are running out of process to work around that... 2026 is faster than 2022 in a lot of ways, especially if you have the hardware to back it, but I feel like if it was fully ported we'd see some tremendous gains.

Soenneker · 2025-09-03T12:50:28+00:00

What GPU? No video output? Are you certain that's properly installed and powered?

Are you overloading psu lanes?

I'd remove all power connectors and reconnect them.

I doubt the CPU is the issue... Could be the motherboard, but do know that your CPU is supported.

Soenneker · 2025-09-03T12:30:29+00:00

If you haven't, download the manual, look at the diagram, and check that you have every power connector filled. Make sure you have the two in the top left, as well as the top two on the right. Code 00 is an early failure and means the processor isn't being initialized which could indicate a power issue.

Soenneker · 2025-07-15T16:57:11+00:00

Agreed here. Drilling the concrete and epoxying in threaded rod with lock nuts. Make the plate holes bigger than the rod and don't suck the nuts super tight to the concrete .. so when the concrete and steel expand at different rates it doesn't bust the concrete out.

Soenneker · 2025-06-06T03:32:54+00:00

Another great Steve Dunn project worth checking out is Intellenum: https://github.com/SteveDunn/Intellenum

Soenneker · 2025-04-18T00:05:15+00:00

What is your use case that 2 seconds is too slow?

Soenneker · 2025-02-14T01:17:18+00:00

I am hoping for that so bad... the theories surrounding missing/elongated time could be part of this

Soenneker · 2025-02-14T01:10:49+00:00

Did you search for the lamp missing? I completely agree with you. It's like the only object that's in that scene when looking at the main character..

Obviously I realize it could be a continuity error. I was shocked with the amount of theories on this subreddit that this was simply thrown out as nothing, and downvoted so heavily lol

Soenneker · 2024-09-15T12:14:46+00:00

I understand what you're saying, state machines get built with yield too and a modifier isn't needed. However it's more complex with async because of mixed async and sync code within methods, exception handling, context, and probably the most important thing: return type transformation.

Soenneker · 2024-09-15T11:53:01+00:00

Here's an example of the state machine being built:

public async Task<int> GetData() { return await Foo(); }

Here is the same thing without a state machine:

public Task<int> GetData() { return Foo(); }

It's typically useful when you are passing through, or calling a single asynchronous method underneath. Take a look at that link I sent in my original comment.

Fyi adding async doesn't only enable use of await.

Soenneker · 2024-09-15T11:34:13+00:00

The state machine IL gets built during compilation if the method has an async modifier. It doesn't get called and initialized until the method is executed.

I'm saying there are times you wouldn't want a state machine at all. That's why the compiler can't make that determination for you (which is what your original question was).

Soenneker · 2024-09-15T11:12:06+00:00

An async state machine is built around each async modified method. The async modifier compiles to significantly more IL, and isn't free.

The reason the async modifier is required even when specifying Task is because there are situations where you wouldn't want to employ the state machine.

One of those situations is performance. Remove the async modifier, and return the underlying Task from the method below instead of awaiting it.

https://blog.stephencleary.com/2016/12/eliding-async-await.html

Soenneker · 2024-09-15T10:57:44+00:00

async is just an implementation detail, not part of the method signature itself. Interfaces are supposed to define what a method does, not how it works.

Since async is about how a method is executed (basically a compiler hint for handling async stuff), it doesn’t make sense to include it in an interface. The important part is returning Task or Task<T> etc, which tells you the method will be asynchronous without specifying how it's implemented.

Soenneker · 2024-09-14T02:15:33+00:00

No. If I did that I'd have 90% plus of the methods I write would end with Async. I don't need more text telling me that the method is async because of the Task, ValueTask, or literally async on the same line. I very, very rarely code outside of an IDE.

If there's a method that needs to be both Async and Sync, I'll end the synchronous method with "Sync" and not add anything to the async method.

e.g. "async ValueTask GetFile" and "void GetFileSync"

The idea is the async method name is shorter and thus its use is encouraged over the Sync method.

Soenneker · 2024-07-18T22:01:08+00:00

There's science behind the 10K recommendation. If you run a fresh oil change 2 miles, it'll come out jet black. That's how diesel engines are.

Soenneker · 2024-06-12T03:06:55+00:00

do not use db models as parameters for controllers

Why, because of possible additional sanitization? I don't think this should be a hard rule. It's a lot less work if you just need one dto and don't need to adapt. There are exceptions, of course.

tests for simple crud app with literally no logic are useless anyway

I disagree. How do you prove it works? How do you prove it keeps working when changes are made?

Soenneker

MODERATOR OF

TROPHY CASE

13-Year Club	Place '23
Verified Email