The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
You should see what you can do with the new .NET Core features. It's become a lot less "allocatey" with the moves to .NET Core 2 and beyond. There are new APIs such as Span<t> and Memory<t> (and a whole lot more) that improve both the speed of working with .NET, and reduce the allocation/GC footprint. I would suggest reading up about these features and the other improvements in .NET Core (and .NET Standard). They are fascinating.
it always comes down to trial and error. make a thing, try a thing, go back and *remake* the thing because DHTML and CSS are funny in a sad kind of way - like an old married couple that hates each other but won't divorce.
is there a better way to do it? I mean other than schlepping it off onto someone else, which is my first choice.
is there some magic to web development that makes it not suck?
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
I have some experience with Betty Blocks, and the HTML and CSS part is indeed quite easy, just drag it on the form.
Everything else sucks, like no source control, back-end code is also drag 'n drop, don't even try the newest front-end frameworks, weird database without a query language (that I know of)...
You can't have your pie and eat it too
Long answer: neither (D)HTML nor CSS were really designed for the purpose they are used for, namely a browser-independent specification of page layout, etc. It is therefore no surprise that HTML development is so kludgy.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.