C# is dying
-
Andrew Zuo[^]:
In the last few years I have become very worried about the fate of C#
"Nobody goes there anymore. It's too crowded" This one won't be appearing in the mailing, as it's on Medium and a lot of people have trouble accessing that site (or disagree with its limitations on reading). However, I didn't want it to not have a chance to be discussed. If you're not able to access it on Medium, try the ripped version[^]. So, why didn't I just post it to the daily newsletter using the ripped version? I dunno. It just didn't feel right.
TTFN - Kent
-
Andrew Zuo[^]:
In the last few years I have become very worried about the fate of C#
"Nobody goes there anymore. It's too crowded" This one won't be appearing in the mailing, as it's on Medium and a lot of people have trouble accessing that site (or disagree with its limitations on reading). However, I didn't want it to not have a chance to be discussed. If you're not able to access it on Medium, try the ripped version[^]. So, why didn't I just post it to the daily newsletter using the ripped version? I dunno. It just didn't feel right.
TTFN - Kent
-
Andrew Zuo[^]:
In the last few years I have become very worried about the fate of C#
"Nobody goes there anymore. It's too crowded" This one won't be appearing in the mailing, as it's on Medium and a lot of people have trouble accessing that site (or disagree with its limitations on reading). However, I didn't want it to not have a chance to be discussed. If you're not able to access it on Medium, try the ripped version[^]. So, why didn't I just post it to the daily newsletter using the ripped version? I dunno. It just didn't feel right.
TTFN - Kent
(Not clicking that.) Just yesterday I was conversing with a VB.net practitioner (he seemed normal otherwise :shrug: ). And I again recalled that the demise of C# in favor of VB.net has been mentioned at least as long ago as 2003. I do still long for the language which is to follow C#, and the framework it uses. Not holding my breath.
Dcontinues to be the language I would learn if I had a reason to. -
Andrew Zuo[^]:
In the last few years I have become very worried about the fate of C#
"Nobody goes there anymore. It's too crowded" This one won't be appearing in the mailing, as it's on Medium and a lot of people have trouble accessing that site (or disagree with its limitations on reading). However, I didn't want it to not have a chance to be discussed. If you're not able to access it on Medium, try the ripped version[^]. So, why didn't I just post it to the daily newsletter using the ripped version? I dunno. It just didn't feel right.
TTFN - Kent
-
(Not clicking that.) Just yesterday I was conversing with a VB.net practitioner (he seemed normal otherwise :shrug: ). And I again recalled that the demise of C# in favor of VB.net has been mentioned at least as long ago as 2003. I do still long for the language which is to follow C#, and the framework it uses. Not holding my breath.
Dcontinues to be the language I would learn if I had a reason to.tl;dr: Cause of death according to the author is "feature creep". :sigh:
TTFN - Kent
-
tl;dr: Cause of death according to the author is "feature creep". :sigh:
TTFN - Kent
Which I can understand. I use C# 3. Many bad decisions have been made. We need a new language which learns from the mistakes.
-
Andrew Zuo[^]:
In the last few years I have become very worried about the fate of C#
"Nobody goes there anymore. It's too crowded" This one won't be appearing in the mailing, as it's on Medium and a lot of people have trouble accessing that site (or disagree with its limitations on reading). However, I didn't want it to not have a chance to be discussed. If you're not able to access it on Medium, try the ripped version[^]. So, why didn't I just post it to the daily newsletter using the ripped version? I dunno. It just didn't feel right.
TTFN - Kent
I didn't click the link, but while I do agree all languages evolve and/or get replaced (just look at the history of them) and so C# will be included in that eventually too... C/C++ is still around. COBOL is still around. ASM is still around. Sure, it's special use cases and perhaps not the cool new thing, but the world doesn't switch overnight. Even though it will switch eventually. As a side note, all languages as we know them today are dying. The next wave of tech will thin the lines of desktop and web development even more. Languages will have to handle issues not originally thought of when the desktop and web were considered widely different. We're trying to make OSes subscription based and like a service for instance. Even JavaScript will meet its fate eventually as WASM gets more and more advanced, able to handle DOM manipulations better, etc. Point is, if you can't embrace change, you're in the wrong industry. AI will change things a lot too. The coders of the future may literally just talk high level to the computer and the computer code itself in the actual language. We already have a rudimentary version of that with [ChatGPT](https://openai.com/blog/chatgpt/).
Jeremy Falcon
-
Andrew Zuo[^]:
In the last few years I have become very worried about the fate of C#
"Nobody goes there anymore. It's too crowded" This one won't be appearing in the mailing, as it's on Medium and a lot of people have trouble accessing that site (or disagree with its limitations on reading). However, I didn't want it to not have a chance to be discussed. If you're not able to access it on Medium, try the ripped version[^]. So, why didn't I just post it to the daily newsletter using the ripped version? I dunno. It just didn't feel right.
TTFN - Kent
The rumors of my demise are greatly exaggerated. C# But seriously speaking - C# is a great language and with every new feature set it becomes better and better. The major features they add are very well thought out and very much in tune with what many people want to be added to the language. The latest case in point are abstract static methods added to the interfaces - one cannot overestimate the importance of it for improving reuse. What was hurting C# before - was the fact that it was tied to Windows OS. But there is no longer such restriction.
Nick Polyak
-
Andrew Zuo[^]:
In the last few years I have become very worried about the fate of C#
"Nobody goes there anymore. It's too crowded" This one won't be appearing in the mailing, as it's on Medium and a lot of people have trouble accessing that site (or disagree with its limitations on reading). However, I didn't want it to not have a chance to be discussed. If you're not able to access it on Medium, try the ripped version[^]. So, why didn't I just post it to the daily newsletter using the ripped version? I dunno. It just didn't feel right.
TTFN - Kent
C# is not dying.
-
Andrew Zuo[^]:
In the last few years I have become very worried about the fate of C#
"Nobody goes there anymore. It's too crowded" This one won't be appearing in the mailing, as it's on Medium and a lot of people have trouble accessing that site (or disagree with its limitations on reading). However, I didn't want it to not have a chance to be discussed. If you're not able to access it on Medium, try the ripped version[^]. So, why didn't I just post it to the daily newsletter using the ripped version? I dunno. It just didn't feel right.
TTFN - Kent
Not going to click this either :-) ... this opinion is "unusual" :-) because, according to TIOBE, for the past 10 years or so C# has always been in the top 5 on the planet, it went up from 12 in 2003 to 8 in 2008 and then it went up again, and it got its steady place there since 2013: 2023: 5 2018: 4 2013: 5 2008: 8 2003: 12 No sign of decline here ...
-
Andrew Zuo[^]:
In the last few years I have become very worried about the fate of C#
"Nobody goes there anymore. It's too crowded" This one won't be appearing in the mailing, as it's on Medium and a lot of people have trouble accessing that site (or disagree with its limitations on reading). However, I didn't want it to not have a chance to be discussed. If you're not able to access it on Medium, try the ripped version[^]. So, why didn't I just post it to the daily newsletter using the ripped version? I dunno. It just didn't feel right.
TTFN - Kent
Dumbass article. Same with the fake Bjarne interview. Bunch-o-crap. Can I have my 10 minutes back??!!??
#SupportHeForShe Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
-
Which I can understand. I use C# 3. Many bad decisions have been made. We need a new language which learns from the mistakes.
PIEBALDconsult wrote:
We need a new language which learns from the mistakes.
As if we (human race) would learn from our mistakes... :doh: :sigh:
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
So his real complaints are that he feels compelled to use the latest and greatest syntactic sugar and isn't getting paid as much to write the same sloppy code as before. Need to find my cricket violin.
-
I must admit though, I do dislike changes that save some smartypants in Redmond from typing a couple of keystrokes and completely change the look and feel of the language.
-
If "var" replaces the same type information that is written in plaintext on the same line, to the right of the equals sign, then I do not see how it makes the code harder to understand. This is typical for an object being initialized by a "new". Saying the same thing twice on the same line is a form of redundancy that I dislike. If you at programming/compile time cannot know the datatype returned e.g. from a LINQ query, so you must ask at runtime about the details of what you got, I do not see any alternative that is obviously easier to understand than "var". Of course "var" is sometimes abused. I've seem examples where the programmer - most likely with a background from script languages - seems to say Oh Goody! Now I can pretend that C# is a typeless language! I am in favor of strict typing. So I cannot agree that "var" is "stupid" - only that there are stupid uses of "var".
-
If "var" replaces the same type information that is written in plaintext on the same line, to the right of the equals sign, then I do not see how it makes the code harder to understand. This is typical for an object being initialized by a "new". Saying the same thing twice on the same line is a form of redundancy that I dislike. If you at programming/compile time cannot know the datatype returned e.g. from a LINQ query, so you must ask at runtime about the details of what you got, I do not see any alternative that is obviously easier to understand than "var". Of course "var" is sometimes abused. I've seem examples where the programmer - most likely with a background from script languages - seems to say Oh Goody! Now I can pretend that C# is a typeless language! I am in favor of strict typing. So I cannot agree that "var" is "stupid" - only that there are stupid uses of "var".
trønderen wrote:
So I cannot agree that "var" is "stupid" - only that there are stupid uses of "var".
Not only for "var", many features could get into your definition
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.