It absolutely should not have been named zeroth() because the reasoning for that is purely pedantic and ignores WHY arrays are 0 indexed. It's not like the people in the early days of writing programming languages were saying "the zeroth item in the array" - they would refer to it using human language because they are humans, not machines. Arrays are 0 indexed because it's more efficient for address location. To get the location in memory of an array item, it's startingAddress + (objectSize * index). If they were 1 indexed, the machine would have to reverse the offset.
Function/Method names, on the other hand, should be written so as to make the most sense to the humans reading and writing the code, because the humans are the only ones that care what the name is. When you have an array or list, it's intuitive to think "I want the first thing in the array" or "I want the last thing in the array)," so it makes sense to use first and last. That also makes them intuitive counterparts (what would be the intuitive counterpart to "zeroth"?).
JustAnotherRando
Pretty sure people have been shitting on AI pretty heavily as well, partly for those reasons (but also for several others).
So I don't think it's the only solution, or that anyone that doesn't care for C# is wrong or anything like that, but it is a suitable language for large segments of development and is both a good career and, in my opinion, rather pleasant to work with. Looking at the languages listed in that list you shared, I see a lot of C, C++, and Java, which I have no interest in working in again unless i have a good reason for it. The other languages there are fine but I never had a big interest in Go (Google's language) - it seems fine, but in my area I don't think there's much of a community around it.
The .NET community is pretty active where I live which is a plus, there are lots of jobs in the language and lots of professionals that are proficient in it. I'm going to try to avoid sharing too specific of information, but I've used C# in industries from healthcare, to automotive, to HR, to fitness. There are absolutely no shortage of companies using the technology - according to Statista, it's the 8th most popular language, and they are including SQL and bash in that listing. I'm not sure I believe that data, but it was the first result I clicked in a very quick Google search.
I agree that popular != good, but if we are going to use "what companies are doing," there are clearly plenty of people that have found it to be the right choice for their projects.
I will say that if your last exposure to .NET was like 5-10 years ago, it's worth taking a look at what it offers now - not necessarily to use it yourself but to at least understand that it does bring a lot to the table. I tend to see a lot of people that make references to C# as it related to .NET Framework (e.g. "you have to use Windows") that haven't been the case since .NET Core came out in 2016. I will absolutely agree that it's not always the right choice and there are aspects to the .NET world (Microsoft has the most obnoxious versioning - .NET Framework up to 4.x -> .NET Core up to 3.1 -> .NET 5 up to 8). And I fully get not wanting to work on it because it's Microsoft because everyone has their brands that want as little to do with as possible, but it is a good object oriented language.
It very much depends on what you're trying to do. C# is pretty great for developing APIs, especially in an enterprise environment involving a lot of business logic. I don't have much of an opinion on Django as I haven't spent enough time looking into it, but I have looked at enough Node.js code to know I don't prefer it for most of the projects I've been involved in.
My Python experience is largely based in working with things like Raspberry Pis, and relatively simple jobs where Python made the job pretty easy. I don't know enough experience with larger Python projects to have a feel for what good architecture in a complex application looks like.
With C#, I can go into a large application using good practices and quickly navigate the code and be productive.
I work in C# and I find it highly preferable over working in Java or C++.
Modern .NET (i.e. .NET Core and later) is cross platform. In fact, .NET APIs now are routinely run in containers not based on Windows.
Yeah, this is one scenario where the principles in F2P games like MOBAs applies to the business world. Focusing only on the top X companies and losing that market share has a cascading effect where it's harder to find competent administrators, it's harder for those administrators to find support online (which then means they have to call for the support they pay for - which while good in the short term for VMWare, is frustrating for the customer, and means that the extra money they're charging has to partially be used to cover techs to provide said report). The little fish in a market like this help to provide what is essentially free troubleshooting online via stack overflow etc. And giving that market share to competitors gives them the cash flow and experience to build a support system online and improve their product, and then win over the big fish.
Olives exist to be pressed and processed for oil. Olive oil is delicious, but I can't stand olives themselves.
When a company stops supporting devices like this, the devices and their documentation and code should be required to enter the public domain. It should not be allowed for assistive devices to become e-waste stuck in a patient's body.
This is also why regulatory agencies have been systematically crippled over the last 40 years or so. Damn near every sector has had their regulatory agencies crippled by some combination of reducing authority, underfunding, and understaffing. When the agencies work, the message is "see, we don't need those regulations anymore because we're taking care of things fine on our own," and when they stop working, the message is "we shouldn't be spending money on these agencies! They don't do anything anyway!"
I think some portions of the company do want to buy these studios to make games. Mostly because they need a regular funnel of titles to put on Game Pass, and the best way to do that is small- to mid-budget games that can generate hype. But then other portions of the company want to chase that big AAA paycheck because big numbers look good, even if ROI isn't as good for that one game versus 3 or 4 smaller titles. And others still only care about what will make the balance sheet look the best for the quarter.
Even smaller companies end up with various "factions" within the org as far as vision and how to best create success (or even how to define success); a company like Microsoft is so fractured that different divisions are unaware of each other's goals and have competing interests.
I'm not trying to defend Microsoft here, I just think this is a consequence of an overly large organization that doesn't have unified goals.
They felt like it? Their brain worded the thought using "his or her"?