3 ms·
Having worked on .NET frameworks up to 4.5, and then vaguely following the evolution of C# since then, it certainly seems like a "new language" in many places.
by DrBazza 5y ago
Having worked on .NET frameworks up to 4.5, and then vaguely following the evolution of C# since then, it certainly seems like a "new language" in many places.
The trouble is that you can still write code in the original language, e.g. don't use the elvis operator or Linq or '?.', which is what is likely to happen if you write a lot of code in other languages too - C++, Java, Kotlin, Python, Javascript. There's a common 'subset' language in all of those that's easy to carry mentally from one to another.
One thing that Intellij/Kotlin has is that if you write "old fashioned Kotlin", there are a lot of IDE inspections that can convert that "old style" code to sort-of idiomatic Kotlin.
- smackeyacky 5y agoOne of my pet gripes of android development is finally accepting a tool upgrade to android studio, only to have it suddenly complain your coding style got deprecated and your warnings become a sea of yellow down the side. Its infuriating. Give me that C# approach any day.
- trissylegs 5y agoVisual Studio and Rider/Resharper has that for C# too.
- DrBazza 5y agoI know about Resharper, but I haven't fired up Visual Studio since 2015 (I think...) so I have no idea what the built-in refactorings are like these days.
- trissylegs 5y agoI remember when I picked up 2019 I found it was much better than previous versions that I used. (In terms of refactoring and other coding assistance)
- kreeben 5y agoVS's built-in refactoring capabilities are very resharper-like. I haven't used resharper for the last decade. There's no need (for me). Resharper's constantly crashing and/or taking up too much resources while it's doing its "solution wide analysis" in the background, causing many a crash, is not something I miss. VS debugging is a bliss. immediate window: god sent. Does VS crash five times per week. Yes. And it sucks every time. And do I swear upon my late father's grave I will migrate away from .net and devote the rest of my life to destroying MS? Also yes. Then all of a sudden a critical bug is found in production that I can reproduce perfectly, locally, and fix seamlessly and I forget about my mission.