8 ms·

What do you mean by avoid looking weak? Like engineers in that community look down on not using the latest features?

general1726 1y ago
There is a FOMO especially around younger developers who wants to use latest, newest and upgrade all frameworks the moment they pop out on Microsoft website. Older developers (like me) have opposite problem and I have been fighting for months to not upgrade .NET4.8 to .NET8 due to compatibility with our current deployment chains etc. In the end I had to admit that using .NET8 for everything is going to work too and is going to give us access to better tools and new tech either through some teething problems.
- riku_iki 1y ago
  It could be because this is the easier way to build up resume and be competitive on the market.
- neonsunset 1y ago
  [dead]
jayd16 1y ago
I think the parent is mostly sour grapes. There is no such community push but like anywhere else, you'll see folks get excited about new toys and then try to force them in to try them. It's not any worse for C# than anything else.
breadwinner 1y ago
> Like engineers in that community look down on not using the latest features? Yes. Engineers use the latest features heavily to demonstrate that their skills are current. One of the worst such features is "var". Some tools even flag your code for not using var when you could. Inappropriate use of "var" makes code harder to read (and even MS documentation says this) and makes code slightly less reliable too.
- enlightens 1y ago
  Ok but var has been around since C# 3.0 in 2007. Love it or hate it, using that keyword in 2025 signals nothing about how current your skills are. https://en.wikipedia.org/wiki/C_Sharp_3.0#Local_variable_type_inference https://en.wikipedia.org/wiki/C_Sharp_3.0#Local_variable_typ...
  - breadwinner 1y ago
    You are right about this not being a new feature. But if you don't use it, it seems like you haven't updated your skills in a while. Besides making the code harder to read, "var" also makes your code less reliable as seen in this example: https://circles.page/567f44465c28b00bf8ed6cf9/Csharp-Type-Inference-Danger https://circles.page/567f44465c28b00bf8ed6cf9/Csharp-Type-In...
    - recursive 1y ago
      SomeMethod().Fire(); has the same "problem". var e = new Employee(); does not. The problem you see is independent from var.
      - breadwinner 1y ago
        You are right, SomeMethod().Fire() has the problem too. But typically you write Employee e = SomeMethod(); e.Fire(); This does NOT have the same problem as var. When you use var you reduce the opportunities for the compiler to catch your bug. So the best practice is to explicitly state the type when possible. It makes the code more readable too. What's more, Microsoft recommends using implicit typing for local variables only when the type of the variable is obvious from the right side of the assignment. See: https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals... But that's not what the community is doing, and some tools (JetBrains Rider) recommend using var whenever possible.
        recursive 1y ago

There is a FOMO especially around younger developers who wants to use latest, newest and upgrade all frameworks the moment they pop out on Microsoft website. Older developers (like me) have opposite problem and I have been fighting for months to not upgrade .NET4.8 to .NET8 due to compatibility with our current deployment chains etc. In the end I had to admit that using .NET8 for everything is going to work too and is going to give us access to better tools and new tech either through some teething problems.

riku_iki 1y ago
It could be because this is the easier way to build up resume and be competitive on the market.
neonsunset 1y ago
[dead]

jayd16 1y ago

I think the parent is mostly sour grapes. There is no such community push but like anywhere else, you'll see folks get excited about new toys and then try to force them in to try them. It's not any worse for C# than anything else.

breadwinner 1y ago

> Like engineers in that community look down on not using the latest features? Yes. Engineers use the latest features heavily to demonstrate that their skills are current. One of the worst such features is "var". Some tools even flag your code for not using var when you could. Inappropriate use of "var" makes code harder to read (and even MS documentation says this) and makes code slightly less reliable too.

enlightens 1y ago
Ok but var has been around since C# 3.0 in 2007. Love it or hate it, using that keyword in 2025 signals nothing about how current your skills are. https://en.wikipedia.org/wiki/C_Sharp_3.0#Local_variable_type_inference https://en.wikipedia.org/wiki/C_Sharp_3.0#Local_variable_typ...
- breadwinner 1y ago
  You are right about this not being a new feature. But if you don't use it, it seems like you haven't updated your skills in a while. Besides making the code harder to read, "var" also makes your code less reliable as seen in this example: https://circles.page/567f44465c28b00bf8ed6cf9/Csharp-Type-Inference-Danger https://circles.page/567f44465c28b00bf8ed6cf9/Csharp-Type-In...
  - recursive 1y ago
    SomeMethod().Fire(); has the same "problem". var e = new Employee(); does not. The problem you see is independent from var.
    - breadwinner 1y ago
      You are right, SomeMethod().Fire() has the problem too. But typically you write Employee e = SomeMethod(); e.Fire(); This does NOT have the same problem as var. When you use var you reduce the opportunities for the compiler to catch your bug. So the best practice is to explicitly state the type when possible. It makes the code more readable too. What's more, Microsoft recommends using implicit typing for local variables only when the type of the variable is obvious from the right side of the assignment. See: https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals... But that's not what the community is doing, and some tools (JetBrains Rider) recommend using var whenever possible.
      - recursive 1y ago