The 2 New Web Application Types Added in .NET 8

[@radekskl]

"Hey everybody I'm naked" - gets me every time

[@DPMiller93]

Ok, I am Not the only one 😂

[@sohampatel1063]

😂

[@conway9214]

😆 Now I can’t unhear this anymore

[@davidcfrogley]

I keep hearing "We just LOST a new course..."

[@shahzaibhassan2777]

🤣 Now I'll keep hearing that

[@mfsbo]

I think you should do performance comparison as its good candidate for few of us separating legacy functions into cheap custom single endpoint.

[@OOpSjm]

The difference is the size of the deployable application. Tree shaking of the webhost

[@ProfessorCodemunkie]

The Empty builder is quite cool. There's a big argument that .NET can be too "magic" at times and you don't know what's happening, so the ability to configure everything yourself and see exactly which features are being enabled is nice.

[@matijs1365]

Great video as always! Would totally like a video about the performance differences!

[@MrRukat]

The performance difference comparison will be a cool stuff. Can't wait.

[@wolle1965]

To answer your question at the end: I'd really like to see the improvements (i.e. benchmarks) of the empty or slim approach in terms of memory footprint and startup time as well (not only total performance) since I am working in a project building a docker based application where each service type runs at minimum in 2 instances. So money for the spent resources is an aspect for the customer.

[@BradJones-pd8gv]

Thanks Nick, this is such a powerful feature. Definitely a performance video, would love to see how you measure the differences. It would also be interesting to see what impact there is on lambda cold start.

[@paca3107]

nice, I am new in .NET (moved from js land) and I really like your content!

[@JohanLangeville]

Would be nice to see a performance comparison between slimBuilder in a normal .NET application and a Native AOT application.

[@umerkle]

I would not only be interested in a performance check, but also in a size comparison. If this is done to make AOT code smaller, how much difference would this mean when you build lets say a containerized AOT app? Also compared to single file compressed publish and different base images...

[@nickchapsas]

There if a video coming trying to create the smaller native api

[@HaoNguyen-km9xj]

The empty look nice, it require to know what we do in our application, no magic at all :)

[@PontusWittenmark]

Looks like the team really wants to score well in those benchmarks :)

[@CharlesBurnsPrime]

A native and dependent benchmark would be fascinating, perhaps with a simple GRPC service as the performance-conscious folks would love to hear that is even faster.

[@gregorymeadows3572]

Reminds me of one of the initial draws of .NET Core, less of what you don't need, but at the app instead of framework level. Performance testing would be great, thanks!

[@cabiste]

We need a video about performance difference

[@todd-carter]

What would be great is a gist of SlimBuilder that adds back everything the normal builder by default.

[@SergeiFedorov77]

It's difficult to express but when I started coding you had to add features that you knew how to code but now you have to know "what you can add" and now you can do it with just calling a method. In my opinion it has obfuscated a lot of the knowledge and also changed what is needed from a developer. The gain is +/- zero in total because the total amount of effort remains the same but the nature of the effort has changed. Yes, you can "get more" faster now but they way to "know" how to add new features has changed. It's like we've gone forward in so many areas but still made it no easier to come to the end result..

[@WelcomeToMyLife888]

Yes, the digging around for how to get things done is seriously time consuming.

[@garcipat]

Should you try slim builder by default and only go back if you really need it?

[@tobiasj8019]

What is that for an api Testing Tool?

[@johnathan398]

I wonder if there are any security considerations to going this route. Are any services missing by default that might keep you safe from attacks?

[@jawadahmed-j6d]

hey nick! there is problem i face alot while using stored procedures or functions and that is returning the nested data. Could you please make one video on it?

[@tenshizer0]

Can you show an option to Swashbukler to generate swagger on AOT (slim) web api?

[@IvanRandomDude]

Ok, so "Configuration over convention:" approach

[@ArgeKumadan]

I wonder how many requests per second it can handle with these new builders and native aot compilation.

[@EdubSi]

Less than before 😂 Native aot seems to be a little slower. But cold starts and bundle size is a lot better

[@aborum75]

Remember that the goal of AOT isn't to improve performance (as of this release); rather, it's to reduce the overall footprint and improve startup.

[@GaryFrancis-q3r]

Isn't the "startup.cs" already disappeared with the introduction of "top level statements"?

[@lorcaranr]

How much of a difference is there on the final executable size.

[@_OsamaAmir]

should have checked the size difference to see how much of an impact it has on building the application

[@nickchapsas]

There will be a video coming dedicated to making the smallest apps

[@der.Schtefan]

I didn't get it below 9.3 MB on Linux. Which is still quite a lot for a simple http server.

[@OOpSjm]

​@@der.Schtefandid you look to see what was included?

[@kenniltv]

@nickchapsas please performance cold starts in that upcoming video. Maybe even aot vs normal (old way without aot) comparison of cold restarts. Bonuspoint also test in AWS lambda/Azure functions app.

[@joseluiseiguren7827]

Please, do the performance testing

[@AftercastGames]

I think I’ve finally figured out why I hate the builder startup pattern so much watching this video. Normally, if I’m presented with a new library, the first thing I’ll do is try to find the class that I need, and use intellisense to look through all of the available functions, which gives me an idea how the library works. That is not an option here, because the functions are so generic, they don’t give you any real information or guidance on how the classes should be used. You pretty much have to know what to type before you start. And at that point, you might as well be using configuration files. 🙄 Great video though. As other have mentioned, I’d like to see side by side performance and exe sizes.

[@aaronkoller8811]

The whole time I wanted to see the relative sizes of each. Bummed we didn't get to see that.

[@bahtiyarozdere9303]

Thanks for the video. How about Blazor?

[@johnny_rain3226]

Yeee thats great and all .. but I miss web forms and winforms😢

[@Serhii_Volchetskyi]

Amazing!

[@Esgarpen]

Let's go, give me the numbers.. size and response-time, what are we looking at?

[@orterves]

No IIS support? Oh noooooooooooo ... Anyway.

[@cabriolex]

.Net8 is all about performance, while IIS is antiperformance. why bother?

[@mateuszkulesza8528]

Why should I care about size in AOT scenario?

[@evancombs5159]

Most people probably do not, but there are always someone working in a limited environment where size matters.

[@spuriousGeek]

I feel like it's slowly turning into C++

[@aweklin]

Hi Nick, thanks for sharing. However, I think this clip isn’t complete as I didn’t see some benchmarks. It’s the main reason I watch your videos 😂, don’t ask, just give us. Meanwhile, you are still owing me (us) DateTime vs DateTimeOffset. Thanks for your contribution.

[@CubiCNooBiC]

Will the real SlimBuilder please stand up? I repeat Will the real SlimBuilder please stand up? We're gonna have a problem here...

[@florianvandillen]

I like your content, but you talk too fast for me. It makes it very hard to follow along.

[@cirusMEDIA]

This video felt almost useless.

[@lucasmegaloja]

1st

[@mariocamspam72]

6th

[@MrBoBrilO]

So basically another useless feature

[@pokpok313]

no. https. support. 😮

[@aborum75]

Just add it if required. Usuaually HTTPS is terminated in other parts of the pipeline.