What .NET Conf means for you as a .NET developer

[@edandersen]

Fun fact: Scott Hanselman hasn't been in a .NET Conf keynote since 2021 😢

[@sajadmalik9097]

Scott Hansleman is awesome.... but yes he is been missing from it... First time watching ur channel and this is the first video I saw... I saw few other videos after this one... great content.. thanks...

[@drancerd]

LOL

[@LeAstrale]

That's unfortunately not my definition of a fun fact 😞 He is usually very good at presenting technical subjects in a low-key and down to earth way.

[@drancerd]

@@LeAstrale For that that reason it's a fun fact!

[@edandersen]

@@LeAstrale hence the crying emoji

[@nickchapsas]

I was actually going to react to my own deleted video couple of months ago and see if I was right or not. I delayed it to see if something would change in .NET 9. I was right. It will be out on Wednesday

[@edandersen]

Thanks for the comment, the real OG 🫡

[@Sergio_Loureiro]

Look who's here!

[@Chiramisudo]

Well done. Comment retracted! @edandersen 4:44 Always be honest and authentic. 😊

[@NotInventedHereShow]

I am honestly cautiously optimistic about Blazor. Yes, there were not a lot of stuff in .NET 9 for Blazor. I consider this a "fix a bunch of stuff under the hood" release. .NET 8 was massive for Blazor (as your "mentioned data show"). Blazor is the default web framework for .NET since .NET 8, pushing Razor Pages and ASP MVC away from the top spot, even if you just want static web pages, and there are no alternative web UI frameworks in the pipelines from Microsoft currently, so I dont see Blazor going away. The Office and Xbox apps and ecosystem existed before Blazor was production ready, so I am not at all surprised Microsoft hasn't rewritten those products in Blazor. They have large teams of react developers building those, it would simply not make sense to force them over to the .NET frontend ecosystem. That Steven Sandersen is working the AI extensions library quite normal, people move around between projects after a bunch of years.

[@edandersen]

Blazor being the default is horrifying. Its web forms all over again, a trap to prevent devs from learning how the web works. Great comment, thanks!

[@junoddufort6288]

@@edandersen and, IMHO, that's why startup almost never ever use Ms technology to build there front-end. At least, it's one reason why.

[@Boss-hn6bf]

@@edandersen So we all have to learn assemblerto learning how computer works? 🤣

[@NotInventedHereShow]

@edandersen but it's not WebForms. Not at all. As you say, WebForms hid a lot from the user, especially in the .NET 2 days, but that's not Blazor at all. Blazor gives you full control over the markup and css, has a very good component model, that is somewhat similar to Vue and React. I think it's great it's the default. Heard from quite a few that have worked with Razor Pages that they prefer the Blazor component model over razor pages, and it's the same both for apps (stateful) and web pages (stateless). The big downside is that it is not as performance in "static web pages" mode compared to mvc and razor pages, there are simply more work being done. So devs have one programming model they need to learn to build everything from web pages to full blown statefull PWAs. Still, not perfect, but pretty darn good.

[@edandersen]

@@NotInventedHereShow Conceptually its webforms IMO - its for people that don't want to learn about the request cycle. Its a very clever abstraction.

[@ottomaier7127]

What I've learned in the last decades: As a developer, you can't rely on any MS technology. If it is good, they throw it in the can, and if the product doesn't really make sense, they will hype it for a year or two. So it doesn't matter what you choose, you'll be screwed for sure.

[@Manix-balu]

Correct, but .net is still better choice for apis and server side apps isn't?

[@ezzeldinmahmoud2174]

@@Manix-balu no even though java is declining i still see them using pure java to host server side apis and it works for years ! as for c# and .NET ? from 2020 to 2024 how many were discarded ? and the so called LONG TERM SUPPORT for .net 7 being smaller than .net 6 and .net 8 being so hyped for nothing . i love microsoft but i can't trust their products for learning to get a job .

[@RichardJames-u9k]

I think Blazor is pretty good to learn and use. I had to rewrite a UWP application and I chose to go down the route of Blazor Hybrid MAUI. Whilst developing, I learnt HTML/CSS skills. The appeal to me was being to write mobile, desktop and web applications all in the same front-end language. As a full stack developer, this just seems more productive being able to code in one language for the front-end and then all .NET in the back. I love the concept of Blazor Hybrid and hope it continues!

[@edandersen]

Blazor Hybrid is very clever and ironically the best feature of MAUI. Thanks for the comment!

[@NickTheCodeMechanic]

Good to hear. To prevent rewrites, I suggest hosting your own baget nuget registry somewhere. I would not recommend azure, as you'll be vendor locked and have to deal with its bs auth system. I host my own baget server on railway, which lets you protect it with just an api key and not the unwieldy behemoth that is Windows auth. Whatever code can be repeatable, like services or maybe even source generators or your own filesystem or linq extensions go great in their own tiny nuget packages. Saves a tonne of time. I have a small library for all the boilerplate or helpers that always just get copy pasted or are my own custom utilities like a grepper and a special regex to model mapper. Mine are named after each major kind of use. CodeMechanic.Types .. .Filesystem .. .Async .. .Ado .. .Bash .. .RegularExpressions .. .Linq .... etc. Having a nuget.config pointing to your registry completes the code recycling loop. If you're doing web, I can share my hot reload script too

[@Mark-D-Inman]

I remember Silverlight, and it wasn't just MS that didn't want it, it was the whole world! Blazor doesn't feel like that to me. The teams that use Blazor seem to like it. I know I really really like. So I hope you're wrong.

[@edandersen]

I am normally wrong. thanks for the comment!

[@keyser456]

Silverlight and Managed DirectX / XNA, as well. I got burned on both those. If they screw me over on Blazor, I'm done with MS.

[@britishjames9415]

I remember it that Silverlight was a casualty of apple banning browser plugins. At that point everyone dropped plugin development not just Microsoft.

[@edandersen]

XNA was so good omg ​@@keyser456

[@zolniu]

@@edandersen XNA is still kind of alive in a form of MonoGame.

[@TechieRathore]

Isn't Aspire's UI written in Blazor Server ? In my opinion Blazor will remain their in background just like MAUI and will come back (hopefully).

[@edandersen]

It is yeah

[@NickTheCodeMechanic]

So, blazor is being slowly buried like MAUI?

[@edandersen]

@@NickTheCodeMechanic Look unless important teams in Microsoft also start using it for big important customer facing projects, it will just naturally fall off.

[@alagarsamyrajamannar5559]

@@edandersen You are forgetting the fact the Fluent UI based components version 5 is coming for Blazor. Widely adopted in LoB applications withing MS.

[@amitkumdixit]

Blazor seems to be fine. I have done few production projects on it.

[@vinylwarmth]

Those projects won't be fine in the future if MS ditch support for it

[@usmanfarooq_pk]

@@vinylwarmth Blazor is not going anywhere in near future. If the project life span is around 10 years then anyone is safe to use blazor. If you think that your project is going to stay here for more than 10 years then I think you are not safe with any technology. You will have to upgrade your source code at some point.

[@Manix-balu]

​@@usmanfarooq_pknot all organization could change their ui code for every 10 years. Especially in banking and telecom sides. We have classic aspx webform applications still. It's very important to choose correct option at the start. Based on the usage and market share react will be the better choice for next few decades . React is moving to server side as well , for me it feels like aspx days in react now. Remix has load, and action method. Which is same as OnLoad and OnPost methods of webforms. Because of server side rendering react becomes easy for dotnet devs. Type script is also easy for c# devs

[@orterves]

​​@@vinylwarmth software doesn't just stop working if support is removed. Blazor has a component approach, which is very amenable to mix and match and progressive migration if a project needs to go in a new direction

[@NickTheCodeMechanic]

​@@vinylwarmthnot if, but when, friend. Invest strongly in the fundamentals of html, css and javascript (not react, it's a cesspool; learn to write vanilla js, try Hydro, alpinejs, and htmx; mix and match them till you understand how they all work together and replace ALL frontend frameworks and blazor; it's possible and soooo worth it!)

[@fatihozgen2886]

Brutal honesty! That's why I love this channel.

[@edandersen]

this website has enough shills

[@georgemilev4831]

Blazor server is actually pretty cool

[@edandersen]

It is a technical masterpiece, the WASM stuff is very very clever too. Should you actually use it though? much more to consider than just how cool it is

[@timexpeachtree]

Have used it in production for 2 years now. Yep sometimes Js Interop is bit of a hassle, feels like gluing together. IMO using UI with dedicated front-end might be easier to start development, but on bright side lot of libraries are coming up in blazor.

[@tsichles]

Yes, but .NET aspire dashboard is written in Blazor. Doesn't this count ? Probably, blazor is more of an intranet / application kind of framework. Finally : congratulations for your effort !

[@tstephansen]

I don’t get the hate for Blazor. We were able to port one of our apps to Mac using Blazor hybrid. This wouldn’t have been possible before.

[@edandersen]

Blazor Hybrid is very clever, but if your app wasnt Blazor in the first place you would t have had that problem. thanks for the comment!

[@MichaelArgentini]

Blazor Hybrid might be the best use case for Blazor. You get a fully native app that only uses a web view for the UI layer. And it's FAST.

[@edandersen]

@MichaelArgentini Blazor Hybrid is great but it shouldn't be tied to MAUI.

[@kasasatimothy8751]

You can also use blazor with tauri it's part of the official templates

[@edandersen]

@@kasasatimothy8751 Oh thats sick actually. Tauri is great.

[@PedroLuisVegadelaRosa]

Thank you for your help and honesty, Ed. I was trying to learn Blazor recently, and now I'll focus on Aspire. I don't want to waste time on something that doesn't have a long-term future.

[@edandersen]

@@PedroLuisVegadelaRosa no worries. Aspire won't help you build an app though, just run one. I'd personally learn Web API with Controllers (MVC) and React.

[@PedroLuisVegadelaRosa]

​@@edandersen Thanks for the advice. What do you think, and what are your suggestions for MVC and Angular?

[@Capsaicinophile]

​@@edandersen Ed, why not minimal API if Microsoft defaults to that nowadays? I am curious 🤔

[@edandersen]

@@Capsaicinophile there is nothing to learn as every project does minimal apis differently.

[@olamilekankareem5390]

@@PedroLuisVegadelaRosa I am interested in the response to your question

[@rankarat]

Yesss, word counting-the pinnacle of scientific methods for forecasting the future. Truly groundbreaking stuff.

[@edandersen]

i'm smart

[@rogerdeutsch5883]

3:19 "The fact that we're now focusing so much on infrastructure concerns instead of software development is a little bit of a bother to me, personally." 👍🏽 Agree, 100%!

[@edandersen]

gotta sell that azure consumption. have you considered splitting your app into 100 azure Functions?

[@youtubevideos415]

I think Blazor is more for writing individual web applications, not website. I wouldn't write my website with Blazor either. But they use Blazor for applications like the Aspire ui

[@anthonychurch1567]

You were talking about the keynote only I realise but so many demos in talks were using Blazor. Do you think the migration to Blazor would be more realistic for Microsoft than other large companies with older apps? I forgot Teams uses Electron.

[@usmanfarooq_pk]

I don't know why people bash Microsoft so much for ditching their development technologies. It's a fast moving domain where same thing is happening with other technologies as well. In android we used to develop apps in Java. Then kotlin came in. Now dart and flutter is also available. AngularJs was replaced by Angular. jQuery is also on its death bed. iOS apps are being developed in swift instead of objective-c

[@edandersen]

People choose Microsoft for the stability. they don't have the brand permission to keep breaking things.

[@asagiai4965]

I think there is a difference between language or tool that inspires the development of other languages. And language you are just trying to destroy. Just because it is not popular or something. Like even if kotlin is good, there still java. Not only that you have to think of the people who have been served with the old technology. So I think it is fair to bash Microsoft if you asked me.

[@coolstorybrooooo7643]

idk man, blazor is amazing

[@RobUttley]

That's very interesting, quite the observation! For various reasons, we never dipped our toes in Blazor. I'm hoping we haven't made a mistake with committing to Maui for our current roadmap (we had reasonable success with Xamarin in the past).

[@edandersen]

it gives me Silverlight vibes

[@RobUttley]

@@edandersen Ha ha absolutely. I was a bit worried a couple of years ago when the most important thing they seemed to be adding to Maui was the Blazor container, but I think there's enough in Maui now for it to have some future. I love WPF, and I'm happy to see that every year it seems to persist, despite whatever prevailing platform-du-jour.

[@ashleyhubbard8854]

@@edandersen Exactly. Like a lot of people, I was "Silverlighted". There really is a lot of issues when selecting Microsoft's latest and greatest. If it isn't mainstream technology then forget it. You can thank me next year for saving your project.

[@edandersen]

@@RobUttley what they did to Xamarin Forms was awful, changed the namespaces and reset the entire ecosystem for no reason.

[@kw4521]

How do you usually switch between windows and mac, installing a windows system or virtual machine using mac?

[@edandersen]

I use a Mac as my host because Macbook Pros are the only laptops that don't suck. I use Windows on ARM in either a Parallels VM running on the Mac (for very light stuff, but the occasional game does work), I remote desktop into a real Windows desktop machine or use Azure Dev Box. The Remote Desktop client for Mac is really good.

[@kw4521]

@@edandersen thanks

[@Manix-balu]

I created same application using various technologies (not a simple one, 15+ pages with 5 pages has high interactivity) Blaor was good at the start, but then gets complex when the codebase grows. I tried same in Remix , astro, and NextJs. Finally settled on nextjs. Remix is also good. But will not choose blazor for real serious project. It is reminds me of silverlight days. My organization de commissioned one of large silverlight project recently after so much struggle. Infact htmx + razor pages could be good too. But i will still choose react and stay away fron MS for ui. We are still Dotnet heavy team for apis.

[@edandersen]

HTMX + MVC Views is 🔥 Thanks for the comment!

[@edoreemmanuel4250]

Choose your technology wisely.....is key

[@user-lk1hg9ev5u]

As a C# lover I prefer C# for the backend for my own satisfaction and React/Angular for the front end for the client's satisfaction as they are imo the best tools for the job

[@edandersen]

agree 100%

[@pkop4]

That Aspire is getting so much investment and support from Microsoft is an argument in favor of Blazor, as the dashboard is written in it.

[@edandersen]

I think if they wrote the Aspire dashboard in anything other than Blazor it would be shocking. Its not the flex for Blazor you think it is. Wake me up when another part of Microsoft uses it for something public facing, not the .NET team.

[@rankarat]

Oh, absolutely, because clearly, the only way to prove your commitment to a framework is to burn down everything you've ever built and rebuild it from scratch. Who cares about practicality or priorities, right? Let's just toss years of work in React out the window, because *obviously*, true loyalty to Blazor means starting over entirely. Makes total sense.

[@edandersen]

I dunno mate, Apple started rewriting their apps in SwiftUI because they believed in it.

[@waitingforyou2082]

Blazor is an amazing product I tried it at a production level. If they are not talking much about it doesn't mean they are abandoning it but it might means its becoming more stable and consistent. In .NET9 the improved performance in blazor is noticable which is quite enough for the time being.

[@edandersen]

glad you are having success with it

[@caseyspaulding]

Great points!! Thanks

[@yvanbrunel9734]

I'm a die hard MAUI guy but really appreciate the honesty. Might look into aspire to integrate in MAUI

[@JeremyBurman]

I don't think this is a great take. How many times was EF Core mentioned this year? Blazor is doing fine and you don't have to keep advertising something that is already established, especially in a year where it's mainly a maintenance release.

[@edandersen]

My point was that after all this time, Blazor is still not being used by other important teams in Microsoft in a public way. Thanks for the comment!

[@alagarsamyrajamannar5559]

My Rule of Thumb: When to Choose React: If you're building a client-facing, global-scale software with a team of developers experienced in .NET backend but with expertise outside of Blazor, and you also have skilled UI/UX designers, React is a better choice. Similarly, if your team has experience in JavaScript or TypeScript along with .NET, React is a suitable option. When to Choose Blazor: If your team lacks significant experience in JavaScript, TypeScript, or other modern frontend frameworks, Blazor is the way to go.

[@edandersen]

Blazor just lets your company put off the problem that nobody on your team has experience with TypeScript and modern frontend. In most cases this tradeoff isn't made properly, and it ends up bad for the project, the company and the developers that go along with it (thats 2 years they could have spent learning something mainstream, like React+TS)

[@waitingforyou2082]

They announced that they rebuilt the copilot with blazor and also the aspire interface, isn't that promising for blazor since they used it themselves??

[@edandersen]

good shout on Copilot, good to know

[@aleksandartrifunovic5142]

That's why copilot crashes after 20 minutes...

[@schoderfactory]

Very insightful. Could you summarize your point of view on us what Aspire really adds?

[@edandersen]

It helps bridge the gap between .net developers and operations, it can auto build you scripts for k8s setups. of course you wouldn't have this problem if you didn't build a distributed system in the first place...

[@schoderfactory]

@@edandersen Thank you for the swift answer. I'm usually rather sceptical, but I watched some videos about Aspire now, inspired by your very funny and to the point video. To be honest, for me it looks like Aspire has the intention and potential to reduce a lot of headache or me as a developer. Am I naive?

[@cissemy]

Any chance blazor will take over .net core mvc ?

[@Gabor-jn9zc]

Already has. Blazor is now the recommended new project type.

[@microcolop]

Just found your channel, awesome content! honest and to the point. Are you planning on making any type of paid course on .NET? if not would you suggest a particular course author?

[@edandersen]

just sign up to Dometrain

[@AhmadAhmadzada-u4v]

Hello, Ed. Great video - thank you for sharing your expertise! I’d love to get your opinion on ASP MVC. While I’m already proficient with APIs, I’m wondering if it’s worth diving deep into MVC with Razor view engine. As you mentioned in this video, even Microsoft developers seem to lean toward React for web development.

[@edandersen]

MVC is brilliant for APIs and server side rendered pages.The pattern is having a comeback too with HTMX (if you remember jQuery unobtrusive ajax then it will be familiar)

[@AhmadAhmadzada-u4v]

@@edandersen So, would you say it’s advisable to be familiar with this technology given its relevance in today’s market? Did I understand that correctly?

[@edandersen]

@@AhmadAhmadzada-u4v yes

[@AhmadAhmadzada-u4v]

@@edandersen Thank you very much!

[@ayotundeayoko5861]

moral of the story - use it only if Microsoft uses it.

[@edandersen]

yes. for their public stuff

[@kastriotgashi]

That's righteously of concern for the future of Blazor. I just started to like and use it, I hope the MS doesn't fail us by dropping it altogether

[@edandersen]

Smells of Silverlight to me

[@kastriotgashi]

@edandersen I've heard many people constantly mentioned Silverlight, saying Blazor is not gonna be like Silverlight. But just because they repeat that often, I'm afraid it could be Freudian slip :)

[@CarrigansGuitarClub]

Very very interesting. I have to admit, I have seen so many Microsoft technologies come and go....and Blazor never caught fire!

[@MichaelArgentini]

The Aspire dashboard is written in Blazor ;)

[@edandersen]

yeah so? if it wasn't it would be an insult to Blazor. any developer UI they make now has to be in Blazor or their messaging fails. Wake me up when something important and public by elsewhere in Microsoft is done in Blazor

[@RoyZASTEROiD]

great content, thank you Ed.

[@edandersen]

Glad you enjoyed it!

[@topsultangamer2573]

Hello sir, I hope you’re doing well. I want to talk about something serious. I’m a business student, but I want to become a .NET developer. Is it possible for someone with a business background and zero knowledge of computer courses to learn .NET? Could you suggest what I should do to get started? Also, do you think learning this skill will affect my career as a business student? I’d really appreciate your advice and hope you can reply to this message.

[@edandersen]

I'd stick to business

[@aqz5905]

Planning to get out from development in .NET

[@topsultangamer2573]

@aqz5905 for why bro!

[@georgedoe7416]

Blazor is perfect

[@edandersen]

It is very clever yes

[@robhunt8378]

I think Blazor has a chance, though let's face it, any framework that goes against the javascript behemoth is always going to have a hard time gaining fraction. Especially when it turns out you have to resort to javascript for some/many things. Javascript stinks BTW. Maui on the other hand... might as well shoot it now.

[@edandersen]

TypeScript makes it palatable. but if they can't convince Microsofts own engineers in other departments to switch then it's all over. Thanks for the comment!

[@hendrykhoza4782]

Yes.. final someone said it... thank you for your honest. even with aspire is still too early for me... I will continue with docker compose till I am really convinced

[@edandersen]

Yeah docker compose does the job. I just wish aspire was 'more', like Django admin or something. Thanks for the comment!

[@madgeek7447]

at least it was not about 'AI' .....

[@edandersen]

oh there was a lot of AI. I just don't want to shill it

[@michael-tsai]

Love it! Thank you for being honest.

[@boredyear9017]

Blazor web/wasm seems to have quite poor loading performance on mobile phones, I don't know if it's because I didn't do it well or if it's a flaw in the blazor itself

[@edandersen]

Interesting, thanks for the comment!

[@aleksandartrifunovic5142]

Mine too, I guess it's js interop

[@VoroninPavel]

They just moved a lot of planned features for Blazor to .NET 10, that's probably why they did not hype it compared to .NET 8 conf. Blazor also depends on developments in WASM standard, for example, WASM GC standardization can be beneficial for Blazor. Conceptually, Aspire is good, I see it as win-win for devs and MSFT.

[@edandersen]

Aspire is pretty good yes. thanks for the comment!

[@toddschavey6736]

What a lazy take on Blazor. Did you bother to notice when you were listing your limited examples of what doesn't use blazor that the thing you do recommend, Aspire... uses blazor. Or was that too inconvenient. Sure if you want to write a spa, react + web API are a no-brainer. however if you want to write a SSR based web platform..Blazor all the way. Nextjs is the closest thing to Blazor in the ja world. Astro kinda rocks though. What Microsoft freaking sucks at is own marketing their stuff. The valley bro also live in their echo chamber. Id gladly throw money at a dotnet clone of Vercel. They built Nextjs..shad/cn...v0...and deployment breeze. Blazor + simple-ui + (??) + Aspire+ wrapper over Azure

[@edandersen]

The whole point of Blazor is the SPA powered by WASM magic which is genius. For SSR just use MVC Views like a normal person...

[@toddschavey6736]

@edandersen nope. MVC. 😷🤢🤮The WASM SPA is the bit that gets laughed at by broader web community. Blazor 8 and beyond offer the interactive islands...just like Nextjs, Remix, and Astro...but better.

[@edandersen]

@@toddschavey6736 the WASM bit is the clever bit. Not sure the point of the rest of Blazor is.

[@AlenHuskic]

You needed also to count "AI". That would be fun to see :)

[@edandersen]

I try to ignore it...

[@WannaBeArmin]

1 maybe stupid question. Does .net core API support Aspire? If yes, can you give me a tutorial link?

[@CoolTebza-eh7ig]

The controls of c# forms are the issue they ain't modern yet, web based apps with integration mobile or desktop apps native app per say, problem they slow 🦥 but if there are possible ways of making things faster. GUI is important aspects of things if the design is not modern than pointless. Remember a language must be build to work with any language outthere

[@svierregger]

My older, wiser self appreciates simplicity over abstraction and maintainability over flashiness. KISS becomes a desirable strategy if you have been a developer for any length of time. .NET excels on the backend but there are many options for the frontend, and I don't believe Microsoft will win the war over C# versus JavaScript on the frontend. I wish Microsoft had instead invested in developing a compiled JavaScript framework where they leveraged TypeScript (similar to C#) and their strength in the IDE and debugging space. If your application runs in a browser, you can not practically avoid understanding Html, CSS and JavaScript, so why not let those technologies shine through in the framework you are selling? As far as Aspire goes, it seems to be a solution in search of a problem, and is primarily designed to sell Azure.

[@edandersen]

They should make TypeScript run on the CLR instead of trying to make C# like TypeScript. Imagine .NET being the fastest TS runtime....

[@alagarsamyrajamannar5559]

Nice video

[@salmanhaider14]

I don't see any reason to NOT use Blazor as a .Net dev. Imo it's a solid alternative to React and Next.js. Yes the WASM size is larger, yes there's signalR issues but that's why you get the flexibility to choose whatever rendermode for whatever component in your application based on its interactivity or usage. The razor syntax also appeals me more than the JSX. It's really a nice React/Next alternative for .Net devs. The .Net 9 was more focused on under the hood fixes and optimizations. Also people are infact using Blazor for production. I myself using it for multiple projects.

[@edandersen]

Learning React and TypeScript properly is much better for your career in the long run, in my humble opinion. Thanks for the comment!

[@salmanhaider14]

@edandersen I agree. In fact I have used React or ts frameworks more than dotnet when it comes to web and mobile.

[@edandersen]

@@salmanhaider14 then you'll also agree that your average dev should learn them first before using Blazor so 1) they actually have a job market to fall back to and 2) they understand the tradeoffs that come with using Blazor

[@salmanhaider14]

@@edandersen Yeah that'll definitely help. Although it's not a must based on your goals ofc

[@Eirenarch]

I personally will die on the Blazor hill if I have to. I don't really mind Aspire but I don't care about it. I don't use containers either, but if I have to I'd rather use Aspire

[@ivcbusinesssystems6613]

*I've had trouble warming up to both Blazor and React, and if I'm to be honest, all of them pale in comparison to the dumped Silverlight!*

[@edandersen]

Silverlight was ahead of it's time

I concur. Have said similar things about MAUI, Blazor and UWP. If Microsoft don't use it in their own applications, then no one else is going to use it. Just think Visual Studio made in UWP or MAUI, or VSCode in Blazor. The Xbox Dashboard (on the console itself) is made in React Native.

[@edandersen]

if an engineer at Apple decided to ship an inbox app in React Native instead of SwiftUI they would be sacked. thanks for the comment!

[@neonmidnight6264]

@@edandersen Fun fact: there are two programs for "cloud drive". One is written in React Native (or was?), another one is written in WinUI 3. Guess which one is by Apple and which one is by Microsoft :)

[@edandersen]

@@neonmidnight6264 Yeah I noticed apple bother to use WinUI 3 but MS cheap out and use React and React Native alot. Just surreal.

[@eugbyte1822]

Well put

[@edandersen]

thank you kindly

[@Funkbassfushion]

So Aspire then.

[@curtmantle7486]

I've been a developer using Microsoft tech for 25 years and MS abandoning the tech they previously flouted as the next big thing is pretty much the only thing you can rely on them for.

[@edandersen]

Silverlight and XNA say hi

[@rubananderson3880]

I'll never use XAML on my own accord so MAUI is a big no no. Unless they change it for something like jetpack compose

[@Krishcode264]

i thought i clicked codewith mosh video ahahah

[@randypenajimenez3893]

I prefer AvaloniaUI or UNO Platform over MAUI, MAUI is full of bugs, the development cycle is too slow because doesnt have a designer. Blazor is good but i prefer .NET CORE MVC or Razor Pages with a JS framework in the client side. You had to talk about the desktop world.

[@edandersen]

Agree, the A team is not on MAUI.

[@जयमहाराष्ट्र24]

They didn't use WPF either for long time. Then tried in VS. Focused switched suddenly on silverligt. Silverlight is dead, WPF is unmaintained. Both were good tech. Avalonia now making WPF depricated. Microsoft is good at rapid development and then killing tech waisting their own work. At least making opensource shall be tried.

[@edandersen]

Eating their own dogfood with WPF in Visual Studio led to lots of improvements in WPF. If they really care about Blazor / Blazor Hybrid they should use it for their web based desktop apps like Teams and Outlook. Thanks for the comment!

[@Radictor44]

RIP to all the started and inbuilt Blazor apps ...

[@rankarat]

What?

[@jonasbarka]

So RIP Aspire? It uses Blazor.

[@arztje]

As a .Net veteran I am happy to report I don't give a crap about Aspire.

[@edandersen]

😱😱😱

[@JerryNixon]

Science!

[@edandersen]

counting mentions in keynotes is indeed the scientific method

[@EzequielRegaldo]

This is why i'm not adopting every new tech from market. Still waiting for results, Blazor + maui looks good, but still buggy and still waiting for massive adoption (if it happens)

[@cdrbvgewvplxsghjuytunurqwfgxvc]

.net aspire seems more like a rugpull. The answear to the question of how you can get more .net projects to stick to expensive azure resources. Wake me up if you can target your own nas with it.

[@edandersen]

you can take the config and build helm charts from it

[@drancerd]

My God, what a waste of language they made with C#, I remember that when I was 14 years old and I was starting to program (2000's) and I didn't know what language to choose, an old programmer knew how to say; _*'Don't worry about the language, but about the framework, that will be the challenge of futures generations'*_.

[@fortunembulazi]

Intereting vidoe indeed. Do you think it's worth my time learning .Net MAUI or just pickup React Native for my app development skills as a .Net developer? I'm skilled in both ReactJS and C# MVC, would you say you give C# MVC the same level of respect as ReactJs or you think ReactJs is just superior?

[@SuperWarZoid]

rip blazor

[@methic-w1l]

Spire conf.

[@Sp1tfire100]

Induses will destroy microsoft, as boeing and intel before

[@sheikhAbdelrahman]

I'm a veteran C# dev (recently learnt Golang). C# is too BLOATED like Windows.

[@edandersen]

the runtime isn't bloated but the language itself is getting sprawling

[@sheikhAbdelrahman]

@@edandersen Sprawling is basically bloated - this is not good, that's why .NET is dying.

[@ayotundeayoko5861]

@@sheikhAbdelrahman lol

[@timexpeachtree]

AOT compiling is basically making it faster for stuff like Minimal APIs

[@thoughtsuponatime847]

I had such a terrible experience with C# that I dropped my project. I’m not ever returning to Microsoft.

[@edandersen]

Bleak, what happened?

[@rub3s]

Thanks for making me depressed.

[@edandersen]

Use Orleans it will cheer you up

[@rub3s]

@@edandersen Stoooooop! 😭😭😭

[@edandersen]

@@rub3s Orleans is amazing tho

[@MuhammetSefaKapısız]

I think you hate Microsoft or .NET

[@edandersen]

Nope. I own shares in MS and want them to be the best

[@keyser456]

It feels like Microsoft hates Microsoft at times. Some of the decisions they make completely undermine things they have been building towards for many years prior. A small but significant (and apparently important) portion of their management has a bad case of "squirrel!" They see something new and both drop and forget everything they had been working on to go chase that squirrel. It's a terrible long-term business strategy and it's driving people away from Microsoft for business.

[@MuhammetSefaKapısız]

​hopes it is just a wrong view of what they think.

[@alagarsamyrajamannar5559]

My Rule of Thumb: When to Choose React: If you're building a client-facing, global-scale software with a team of developers experienced in .NET backend but with expertise outside of Blazor, and you also have skilled UI/UX designers, React is a better choice. Similarly, if your team has experience in JavaScript or TypeScript along with .NET, React is a suitable option. When to Choose Blazor: If your team lacks significant experience in JavaScript, TypeScript, or other modern frontend frameworks, Blazor is the way to go.