Comment by breadwinner
1 day ago
> Nobody is completely immune to trends and fads, but the SQLite developers work hard to avoid being sucked into the latest programming fashion.
So good to see this. I have seen so many developers use the latest C# features heavily, to avoid looking weak.
The second sentence is also very good to see:
> Our aim is to produce timeless code that will be readable, understandable, and maintainable by programmers who have not yet been born.
What do you mean by avoid looking weak? Like engineers in that community look down on not using the latest features?
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.
It could be because this is the easier way to build up resume and be competitive on the market.
[dead]
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.
> 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.
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_typ...
8 replies →
Funny. I don’t need to work hard for that at all. It comes naturally to me. It obviously has its pros and cons, but to me, a shiny new tech has to prove itself first in order to deserve my attention.
There are, occasionally, the “wow, I got to have that” moments and those are great, but rare.
I stopped using C# 10+ years ago, but I remember wanting to update the framework and use the latest thing (linq to objects) because it made code a lot more concise.
I have an observation about this: everybody wants a small upgrade that makes it easy for them to make their code a little more concise;
But somehow, almost no one wants a language that is already super-terse in the first place (like Lisp or APL- family).
And yes, that requires a paradigm change to make the most of it - but so does e.g. LINQ.
It’s about the journey, not about the destination.
I can see someone defending Ruby as concise (having the ability to chain different transformations) and simple to write in (low verbosity). Lisp? Define a class and do some map/filter/reduce. Lisp is verbose. Sometimes even worse than Java21 these days.
Just put the equivalent code side by side and look. You would be surprised at how much verbosity you choose to ignore.