Here's the list of new features covered in the video! 0:48 Record structs and with expressions 4:15 Anonymous types 4:50 Custom parameterless constructor for structs 6:50 Field and property initializers for structs 7:53 File-scoped namespace declaration 10:05 Global using directives 12:09 Implicit using directives 14:28 Lambda improvements 21:12 Type inference for lambdas and method groups 22:50 Interpolated strings performance optimizations
These two old programmers are a pleasure to listen. They have that thing about them that says, yeah, been there, done that, and now they are just having fun with the thing they do.
Would be so much better if when the code is changed by the speaker, the screen shows that code and not the speaker looking into a screen which we can't see...
LOL! So far all the "new features" offer very little to no value to me. They merely reduce the amount of typing required. I never heard anyone complain about Using statements as being too verbose or taking too much screen space, nor has anyone wished the compiler could infer types better. What I wish C# had was support for algebraic types, which are very powerful and would definitely enhance the development process.
I have a 28" 16:9 monitor, 4K (because 16:10 or 3:4 isn't really an option anymore. If I make my visual studio fullscreen most of the time half the editor window on the right side of my code is white and empty. And you guys are complaining about removing those few idents on the left side... And then you guys are complaining about vertical space, a few usings in the beginning. Half the foreign projects I see have like a big comments section on top, and default installation and yours too, add a line of 'reference' to every line. Talking about priorities...
Just my 2 cents, but i really dislike the camera work here. The constant jumping from code to presenters to different angles of them to zoomed out panning shots. Maybe I'm just old, but that was distracting af, and I could barely read and appreciate the code without pausing every few seconds. I also dislike the presentation style of some of the other presenters. Especially the ones on the Minimal API talk. Cringey and full of fluff. At least these two are coherent and somewhat straight-to-the-point
what' the problem to simplify delegate even more? Let's say var a = => 3 : 4; is it obvious that is Func a = (b) => b ? 3 : 4; ? Or to be more precise let's write var a = _ => ? 3 : 4; What do you think?
#dotNET what do you recommend, if we are using global using and we have say many projects/files and only one project/file have namespace conflict. How we can handle such scenario ? Should conflicted namespace be added explicitly in each project/file or is there a way to resolve conflict in conflicted file itself.
Thanks for all the good stuff you have brought to the language during its development! I have been using it since it's release for almost 20 years now! But these small alternative ways of writing things that was already simple enough is not very helpful in my opinion. As a developer I strongly favor consistency over slightly less verbose alternatives. I wish you could focus more on fewer features that really makes a difference in what we can do. There are many more doors to open!
I don't either. I'm not seeing why they don't just roll that functionality directly into the type system rather than add a new "thing" that can be either a class or a struct.
@@keithpatrick156 at this point a record is basically just a normal class anyway ... The only thing that's changing is how they are used in code. Are they doing something different in the compiler or how the memory is allocated?
C# Becomes more and more VB. It supports more and more bad coding behaviours. If you need static initializers for a struct use a factory, not a struct-constructor.
Ok here is a joke for you. Why do java developers wear glasses? because they see sharp enough not to bring in every other kind of programming paradigm in one language. get it? No? ok I will see my self out.
I agree. It becomes cultish and only the cognoscenti understand it; and they love that of course. Meanwhile industry needs maintainable code where there is only _one_ way to skin any given cat. If there are two ways to write some code then one of them is wrong and shouldn't be in the language.
instead of destroying the language syntax . focus on performance and improvements . everybody used to love c# because most of them loved the beautiful java like syntax , now it's all gone , I hate c# now ,
@Daniel Prokhorov Your reply is very stupid. My comment would make a future video better. Yours??? Also, I wanna see who is the cry baby me or you: let's meet and say this to me face to face. C'mon, I can deal with your low level kind, np!
@@RenegadeVile Lot's of frivolous code reduction features and no real improvements in c#'s expressiveness. I've never heard anyone complain about Using or namespace statements statements as being particularly verbose. Parameterized strings, on the other hand, has been a god send feature and enhances the developer experience. I would be more excited if they supported algebraic types like F# and Swift as it would improve code quality.
@@bobweiram6321 Whether true or not, that is not killing the language. This guy said they are killing the language and I want to hear from HIM, why he thinks that.
Here's the list of new features covered in the video!
0:48 Record structs and with expressions
4:15 Anonymous types
4:50 Custom parameterless constructor for structs
6:50 Field and property initializers for structs
7:53 File-scoped namespace declaration
10:05 Global using directives
12:09 Implicit using directives
14:28 Lambda improvements
21:12 Type inference for lambdas and method groups
22:50 Interpolated strings performance optimizations
thank you, the clip is a nightmare, just a long story of BLA
Thanks a lot, hero!
You deserve a medal man
This is VERY helpful!!!
I have no idea who green lit this rambling, but they need to stop and lay things out like you have!
These two old programmers are a pleasure to listen. They have that thing about them that says, yeah, been there, done that, and now they are just having fun with the thing they do.
They look young to me :)
*I love C#*. You guys take great features from other languages and implement them in a clean way.
Every time when converting to block-scoped namespace and the indentation jumps a level back my heart jumps as well. Love it! ❤️
I love the direction C# is heading. Definitely my cup of tea. Great work!
Chapters or timestamps would help a lot.
Dotnet conf is my new Super Bowl! Cheers
Really cool and in-depth stuff guys. Thanks!
Would be so much better if when the code is changed by the speaker, the screen shows that code and not the speaker looking into a screen which we can't see...
Jokes on you: I never put 4 spaces at the beginning of my files lines. I use 1 tab.
Like every non-psychopath developer.
Thanks for all the great videos!
when do we get file-level classes?
What happend to static interface methods and generic math improvements? :(
Nice intro into some of the new features
wow, these guys really did some great work on the language didnt they!
Demo Driven Design 😎
LOL! So far all the "new features" offer very little to no value to me. They merely reduce the amount of typing required. I never heard anyone complain about Using statements as being too verbose or taking too much screen space, nor has anyone wished the compiler could infer types better. What I wish C# had was support for algebraic types, which are very powerful and would definitely enhance the development process.
@@bobweiram6321 It might not be groundbreaking, but it's still handy stuff. Not sure what the big deal is.
Man i love c#
I have a 28" 16:9 monitor, 4K (because 16:10 or 3:4 isn't really an option anymore. If I make my visual studio fullscreen most of the time half the editor window on the right side of my code is white and empty. And you guys are complaining about removing those few idents on the left side...
And then you guys are complaining about vertical space, a few usings in the beginning. Half the foreign projects I see have like a big comments section on top, and default installation and yours too, add a line of 'reference' to every line.
Talking about priorities...
some features are copied from F# which is a good thing
Just my 2 cents, but i really dislike the camera work here. The constant jumping from code to presenters to different angles of them to zoomed out panning shots.
Maybe I'm just old, but that was distracting af, and I could barely read and appreciate the code without pausing every few seconds.
I also dislike the presentation style of some of the other presenters.
Especially the ones on the Minimal API talk. Cringey and full of fluff.
At least these two are coherent and somewhat straight-to-the-point
And that animated background with the space ship flying about on loop
what' the problem to simplify delegate even more? Let's say var a = => 3 : 4; is it obvious that is Func a = (b) => b ? 3 : 4; ? Or to be more precise let's write var a = _ => ? 3 : 4; What do you think?
08:24 - The programming meta in 2022 for sure
#dotNET what do you recommend, if we are using global using and we have say many projects/files and only one project/file have namespace conflict. How we can handle such scenario ? Should conflicted namespace be added explicitly in each project/file or is there a way to resolve conflict in conflicted file itself.
How do I call methods in c sharp 10
a good online code c# 10 manual??
We just gained some serious real state in our code files.
Thanks
Thanks for all the good stuff you have brought to the language during its development! I have been using it since it's release for almost 20 years now! But these small alternative ways of writing things that was already simple enough is not very helpful in my opinion. As a developer I strongly favor consistency over slightly less verbose alternatives. I wish you could focus more on fewer features that really makes a difference in what we can do. There are many more doors to open!
As a developer, I favor brevity and simpicity. And also I want C# to stay competitive. They are doing the right thing.
Can we have anonymous classes derive from another class
How you do the arrow symbol (⇒) insted of =>?
It's because of the font. They are the same, but because of the font looks like an actual arrow.
try "Cascadia Code" font
But how about record interfaces? and record enums? :)
Should be able to use an interface,right?
What font does he use?
Fira Code
@@jatin.sanghvi I think it's the "Cascadia Code" font.
@@Печенькасмаком-й3ъ Check the 'g' in 'get;'. Not Cascadia Code
My first love
"maybe" already
I still don't get the point to records.
Am I alone with this?
I don't either. I'm not seeing why they don't just roll that functionality directly into the type system rather than add a new "thing" that can be either a class or a struct.
@@keithpatrick156 at this point a record is basically just a normal class anyway ... The only thing that's changing is how they are used in code.
Are they doing something different in the compiler or how the memory is allocated?
I would like to see the intelliSense to appear again when I use backspace to modify in C# -- just as it is in VB.
those of us who have been around remember record and with in Pascal
I think this mollycoddle approach for new C# programmers will really bite the community in the butt later down the line.
Someone can answer about c# performance? Which language has better performance: Java or C#?
do not troll
@@psdmaniac it is not a troll. Is there a comparative benchmark anywhere? I want to migrate a project from Java to C#.
@@lcfb2009 6:20 => ua-cam.com/video/AFNujHJfMtU/v-deo.html
C# Becomes more and more VB. It supports more and more bad coding behaviours. If you need static initializers for a struct use a factory, not a struct-constructor.
Ok here is a joke for you.
Why do java developers wear glasses?
because they see sharp enough not to bring in every other kind of programming paradigm in one language.
get it? No?
ok I will see my self out.
LOL!
If MS is really interested in reclaiming vertical space, they should consider defaulting opening braces to the end of the previous line.
Microsoft pays people to promote C#?
Making syntax less clear in the name of "reducing code" is the surefire way to tell a language is on path to hell
I agree. It becomes cultish and only the cognoscenti understand it; and they love that of course. Meanwhile industry needs maintainable code where there is only _one_ way to skin any given cat. If there are two ways to write some code then one of them is wrong and shouldn't be in the language.
instead of destroying the language syntax . focus on performance and improvements . everybody used to love c# because most of them loved the beautiful java like syntax , now it's all gone , I hate c# now ,
Thanks for using DARK MODE - next time. My eyes are destroyed.
@Daniel Prokhorov Your reply is very stupid. My comment would make a future video better. Yours??? Also, I wanna see who is the cry baby me or you: let's meet and say this to me face to face. C'mon, I can deal with your low level kind, np!
Killing the language goes on.
How so?
@@RenegadeVile Lot's of frivolous code reduction features and no real improvements in c#'s expressiveness. I've never heard anyone complain about Using or namespace statements statements as being particularly verbose. Parameterized strings, on the other hand, has been a god send feature and enhances the developer experience. I would be more excited if they supported algebraic types like F# and Swift as it would improve code quality.
@@bobweiram6321 Whether true or not, that is not killing the language. This guy said they are killing the language and I want to hear from HIM, why he thinks that.
@@RenegadeVile I don't know we will get an answer from Pavel Svec anytime soon, let's wait and see. Please like this comment when that happens.
@@bobweiram6321 I'm afraid I have to disagree. If you have not heard anyone complain about the verbosity of C# perhaps you have not been listening?