Is it called string interpolation because it... calculates values in between the start and end of the string? Kind of a stretch for me, confused me at first when i heard that name (although i already knew the concept behind it).
If you forget a "}" at the end of a function, will the compiler assume that the next function after it is a local function instead and complain about the missing bracket only at the very end, far away from where your error is? Would make reading errors harder.
Great speech! IMHO C# becomes really old "by design"... it's aging language bloated by features from wide variety of approaches... Jack of all trades, master of none. And you're right! We have only limited amount of keystrokes in our life. That's reason why I chose F# for .NET and expression based functional languages in general :)
So tell me aspects where F# is weaker than C#... except general support, because C# is flagship of .NET. And maybe lack of NullReferenceException in idiomatic code :D... F# is multipardigm Functional First language, not purely functional like Haskell. And you can use .NET assemblies like from C#. And you can even write imperative OOP like in C# if you want - there are lots of reasons to do that and F# does not constrains you like C# when you want to write functionally. Just look at new features from C# vNext and look what was supported in F# for years... Even pretty low level language like RUST supports ADT and features from more "Domain modeling ready" languages like F#... What about Swift and Kotlin? Those are general purpose languages, so try to compare them to C#... C# begins to be limited by its own history and late 90's design. I ask - why tuples now, when you have comfortable out params? Async await... yup, those are just hardly trimmed ideas from F# (computation expressions). Traits support in C# now after years? What's the point (maybe Android things in Xamarin)? Non nullable objects - just warnings? I am big fan of .NET, I've been living with programming in times of Visual Basic 3 and 6 so I lived that .NET hype, and C# is now my main language. I like it (mainly thanks to ReSharper) but I have lot of complaints. Please people, don't live in C# (and .NET) bubble like lot of others and look at beautiful world around you. Inspire ;).
![Lp. Сердце Вселенной #60 РОЖДЕНИЕ ЛОЛОЛОШКИ [Финал] • Майнкрафт](http://i.ytimg.com/vi/YoR0pAV9FVQ/mqdefault.jpg)
Nice having the history bit of the different features.
Kinda miss the old days of so much manual coding :)
Amazing great talker!
Is it called string interpolation because it... calculates values in between the start and end of the string? Kind of a stretch for me, confused me at first when i heard that name (although i already knew the concept behind it).
If you forget a "}" at the end of a function, will the compiler assume that the next function after it is a local function instead and complain about the missing bracket only at the very end, far away from where your error is? Would make reading errors harder.
Not if you are using access modifiers (private, public, etc) at the start of your class member methods
Awesome
The volume sucks. There might be something good though.
Great speech!
IMHO C# becomes really old "by design"... it's aging language bloated by features from wide variety of approaches... Jack of all trades, master of none.
And you're right! We have only limited amount of keystrokes in our life. That's reason why I chose F# for .NET and expression based functional languages in general :)
So tell me aspects where F# is weaker than C#... except general support, because C# is flagship of .NET. And maybe lack of NullReferenceException in idiomatic code :D...
F# is multipardigm Functional First language, not purely functional like Haskell. And you can use .NET assemblies like from C#. And you can even write imperative OOP like in C# if you want - there are lots of reasons to do that and F# does not constrains you like C# when you want to write functionally.
Just look at new features from C# vNext and look what was supported in F# for years... Even pretty low level language like RUST supports ADT and features from more "Domain modeling ready" languages like F#... What about Swift and Kotlin? Those are general purpose languages, so try to compare them to C#...
C# begins to be limited by its own history and late 90's design.
I ask - why tuples now, when you have comfortable out params? Async await... yup, those are just hardly trimmed ideas from F# (computation expressions). Traits support in C# now after years? What's the point (maybe Android things in Xamarin)? Non nullable objects - just warnings?
I am big fan of .NET, I've been living with programming in times of Visual Basic 3 and 6 so I lived that .NET hype, and C# is now my main language. I like it (mainly thanks to ReSharper) but I have lot of complaints.
Please people, don't live in C# (and .NET) bubble like lot of others and look at beautiful world around you. Inspire ;).
BTW it's not an X, it's a roman numeral...
C# won't be done until it's completely unreadable ;)
"Most of the new features are just syntactic sugar that comes at the price of clarity." Yes++