DEV Community

Discussion on: .Net developers how did you guys do it

peerreynders profile image

The goal was to easily attract Desktop developers in the world of web development.

A poster child for how tailored DX can push a product in totally the wrong direction especially when the abstractions introduced only serve to appeal to the familiarity/preference of the developer rather than streamlining the underlying platform and/or problem domain.

webforms that's the dumbest thing ever.

You feel this way because you aren't representative the target audience of ASP.NET WebForms. So the technology violates your sense of familiarity. More often than not familiarity gets in the way either by rejecting valid but foreign perspectives or leading to abstractions that are ill suited to the problem being solved.

Some people seem to be able to just "wing it" but typically that just delays the inevitable meltdown. You're going to have to put the React mindset aside and approach this differently. As wasteful as it may seem investing, at least on a high level, some time to understand what is happening under the hood during compile and run time should build the necessary mental model to grasp some of the reasoning behind the WebForms tooling (however ill-conceived) and how it needs to be manipulated to do what it was created to do.

Aside: Did ASP.NET Web Forms Need to Die?

And while you may be excited now there is a good chance (at least in my opinion) that Blazor based technologies will primarily be used for internal enterprise applications (there will always be exceptions)—client (WebAssembly) Blazor tends to lead to large initial downloads while server Blazor uses the network heavily; neither of which is a problem inside the enterprise but can be an issue on the public web when connection quality and client device computational capabilities of your target audience are unknown or (often enough) poor. (The Fallacies of Distributed Computing (Applied to Front-End Performance) - technology changes, physics don't).

I guess this is when some people start programming on their own time—to remind themselves that it can be interesting (and to get ready to bail out if necessary).