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

preview_player
Показать описание
I watched .NET Conf 2024 so you don't have to. What can we take away from it? The answer might (not) surprise you.

0:12 .NET Conf 2024 recap
1:22 Analyzing the rise and fall of various .NET Technologies
3:37 The future of Blazor
5:04 Should you actually use .NET Aspire?

#dotnet #dotnetconf #csharp
Рекомендации по теме
Комментарии
Автор

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

edandersen
Автор

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

nickchapsas
Автор

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!

RichardJames-uk
Автор

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

fatihozgen
Автор

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

amitkumdixit
Автор

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.

NotInventedHereShow
Автор

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.

ottomaier
Автор

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.

Mark-D-Inman
Автор

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 !

tsichles
Автор

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).

TechieRathore
Автор

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.

PedroLuisVegadelaRosa
Автор

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.

tstephansen
Автор

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%!

rogerdeutsch
Автор

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

youtubevideos
Автор

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.

anthonychurch
Автор

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

yvanbrunel
Автор

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.

waitingforyou
Автор

Blazor is perfect <3, please continue in .NET 10 !!!

georgedoe
Автор

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).

RobUttley
Автор

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

CarrigansGuitarClub
welcome to shbcf.ru