Thoughts on this? I'm experienced with C#, is it good for getting in web development?

>>106140646 (OP)
you should start with web api first then move on to blazor otherwise you'll get confused real fast

>>106140646 (OP)
> is it good for getting in web development?
Nothing is enough for web development. Look at the job market.
You'll likely see a lot of TS and NPM stuff. So why waste your time with MS tech?

I'm a C#/.NET dev, and I feel it's inadequate. It's far and away the slowest performer on the frontend scene and doesn't get enough attention from Microsoft. This is because converting C# to JavaScript (and vice versa) is an expensive process. I use Angular instead since it's the closest thing to .NET style OOP development on the frontend.

>>106140703
I doesn't convert source code. It's a bastard child running .NET IL on a WASM CLR that provides a way for WASM/JS glue

>>106140646 (OP)
This is what I hated about the MS stack.
…more incompatibilities as changes for “blazor” get mixed up with the last 3 fads.
I wouldn’t touch it with a 10 foot pole.
Name reminds me of the old internet meme. What a bunch of tards.

>>106140646 (OP)
It's decent enough to quickly create an internal site. No one sane would use it to create their entire web platform in blazor. You'll never get a job on pure blazor alone.

svelte except it's c#, neat. not neat enough to make me jump frameworks again.

Razor, Blazor, Mazor, Phaser... why can't Microsoft ever stick to anything? Same with WPF/UWP/WinUI123/MAUI/LGBTQ+ and whatever other ten desktop frameworks some intern shit out and became an official product left to fester forever.

>>106140646 (OP)
I like using it.

>>106141172

being a huge dinosaur corporation where they have the resources to just keep spinning off a new tech seems to be a likely culprit. Being forced to go to the mats for your singular products is important. For Microsoft it's just more lazy R&D.

>>106140646 (OP)
The Blazor component lifecycle is fucking retarded IMO, especially using Dispose() for teardown instead of having a dedicated method symmetric with the init methods. And the retarded threading model allows dispose to interleave with other lifecycle methods and time you await an uncompleted task. This also means you can't queue something to run after the current lifecycle method; it might run after you await something. In short, it's even more complex and retarded than the Android activity lifecycle that filtered so many devs.

>>106141585
*any time

It is total garbage.

>>106141172
I guarantee you it's always some idiot coming up with a new idea for job security, though that didn't help the guy who rewrote the typescript compiler

>>106141982
More like some jeet with 2-3 years of experience reads a blog post about a design pattern and rushes to implement it with zero regard for evolving the API in a backward-compatible way.

>>106141982
That guy had somewhere else to Go.

>>106142593
Carlos!

It's like other wasn't frontend things. Slow and large. As long as you need JavaScript to do basic dom shit, it's over for you.

>>106142809
>wasn't
ffs
WASM

I used to 4/20 blaze it but now I 24/7 blazor. 10/10 would recommend

>>106142593

>>106140646 (OP)

I did a simple trial of Blazor... too much shit going on for me.

I prefer Python with Flask or FastAPI... and using something like Vue on the front end. All the C# and Java slop seems like they have 10000 config files, and various abstractions for no reason.

>>106140646 (OP)
It's getting better with each iteration. WASM is slow af though, only use if you don't have decent servers
JS isn't really needed unless you wanna do something gimmicky

>>106140646 (OP)
Very few companies use it. Stick to the angular + netcore combo.

>>106140646 (OP)
Blazor is the best thing ever. Finally you can develop the full stack in a single statically typed language.

>>106140646 (OP)
The only reason this exists is so that C# devs can avoid learning frontend development. It fucking sucks that it even exists, its not compatible with anything, and is unsuitable beyond the most basic internal websites.

>>106140646 (OP)
>C#

If you're white then don't, otherwise - welcome saaar, it's the best language in the world.

It's very basic, buggy and has a lot of obscure bugs.
Community is kinda of shit (boomers, non even the smart kind), It's not worth to learn int IMHO, I have a presonal project (20k loc), and it's very frustrating to work with, to many obscure behaviors and bugs, libraries are very limited, so you implement a lot of baisc or bioilerplate stuff by yourself, also it's very resource heavy on the server, so you have to overly optimize simple stuff.

C# for the web is very clunky, you can tell it's a server language and at the end you end up missing the simple stupid javascript.

You never know on what thread you are doing stuff, asyncronous operation act weird on server, automatic rendering is weird (mostly for the thread problem) so you end up sprinkling StateHasChanged everywhere, Blazor also foces you to rely too much on db for state (too cluky to handle in memory), so you end up eating the db away, caching helps, but it's still a problem.

It is at the end a Microsoft product, and shares the same problems as every ms product, It will never truly be complete, and will always be a little broken and convoluted for no reason.


Next project I will probably just use minimal apis and vue and fuck it, maybe just Next js if I really want to learn it.

>>106144671
Why should frontend even be separated from backend?

>>106140646 (OP)
IMA 1337 BLAZ0RZ B-)
BLAZ1N6 UR UI B-)
SO COOL))

>>106145764
It shouldn't, that's why static HTML is superior. Forms should be enough for interactivity, with maybe some 5 line jquery wizardry

>>106140734
Ewww

>>106144671
And Nodejs exists only for the opposite

>>106140646 (OP)
>good
it’s decent
>bad
it’s microsoft so every decision made funnels you towards visual studio which fuels you into ms everything, ie it’s a walled garden but everything except excel sucks in there

>>106143697
They usually make sense if you're already steeped in the ecosystem that spawned them. Coming into them new is painful because there's so much 'local culture' you have to learn to be even minimally effective.
>>106143717
>It's getting better with each iteration.
That's the problem with so much of what Microsoft puts out now. You're constantly told the next version will be better. Your current pains will be addressed, you just have to be patient. And when it isn't in the latest version? Well, a new version will come out this time next year. Maybe it will be in that release. Meanwhile people who are doing LOB systems are getting screamed at by those above them for a solution. They don't care about what internal politics at Microsoft are starving the framework of the resources it needs. They just want the company's sprockets inventory app to work because selling sprockets is what the company does.

>>106148009
This isn't really true, .NET works well with a lot of stuff, and dotnet CLI is kino.

>>106144805
hit the nail on the head.
.NET is full of boomers who don't want to learn anything.

>>106147981
true, but node is about 10x as popular as ASP.NET despite that

>>106143697

>Python

just don't. At least do TypeScript and Node.

>>106147981

Pretty much. Node was turning JS/TS into a server language. Blazor is turning C# into a frontend language. Personally, and this is speaking as a primarily C# dev, Node + TS is the better full stack solution. Blazor is too cluttered, slow, incomplete and it's simply unpalatable in the modern frontend heavy age.

With that said, if you're going to do separate layers C# is still great server side. It's just, if you only want your engineers to know and master one language (which is a good idea imo), you might as well just go with Node + TS.

>>106144671
It makes no sense, because at the end of the day you are still writing html, css and js. You are not avoiding shit, or maybe on a second thought you are avoiding NPM and all the JS ecosystem stuff, but in exchange you'll need to learn some highly specific stuff, that applies literally nowhere else.
They got the component model right (react-like), that much i'll give them.

>>106149542
With blazor, I have literally never used JS.

>b-b-but you can frontend in C#
yes, and? why should i? seems dumb.
and typescript is very close to C# too. you don't to learn that much.

>>106140646 (OP)
i like C#, but this shit just doesn't work.
use angular, its the best js framework i know.

>>106149542

In fairness the .NET ecosystem and dependency environment is a lot more stable and comfortable than the wildness that is node/npm

everytime I hear the argument between frontend and backend in dev, I find it's a mix. Backend devs hate frontend cause it's silly loose shit. And frontend devs hate backend cause they cant fathom anything past their mess of javascript.

Im on the side of backend devs cause they at least know real programming.

>>106140646 (OP)
It's alright, but there's a reason Microsoft isn't really using it for any major project yet and why even .NET e-celebs are largely ignoring it. It's not quite there yet. Stick to MVC/Razor pages or make an SPA with TS.

>>106140646 (OP)
>2025
>still no WYSIWYG editor for maui metro xaml trash
grimming

>>106140703
they are too busy with ai to care about anything else, in nutella we trust