C# for new projects? Wise choice in the new cloud world?

[eek]

The thing is all managed services in AWS run on Linux only. Yes you can run AWS Lambda using .Net core on Linux, but the results of running .Net on Windows isn't always the same as running .Net on Linux. For example, all locale names and codes are different between the OS.

C# is a 2nd class citizen to AWS managed cloud services.

If the primary goal is a fully managed AWS solution, C# and .Net core are not the best fit.

Python is probably the best language for 100% AWS solutions.

But if you look at azure C# is probably the best choice and python 3rd after all the various Javascript implementations.

[mogga71]

I have never understood these types of discussion. Just choose the most appropriate language for the task in-front of you. C# is actually pretty good. It is well maintained, tried and tested and well integrated with a major operating system. 5 minutes googling shows that around 25% of servers serving the internet are windows. That is a massive number of windows servers. Why wouldn't you choose a programming language created by the same vendor as your OS?

C# isn't going anywhere. If you want to write desktop app (and yes, even now people use desktop apps), what is there better for your solution?

My current project is implemented all in GO. It works for us, tiny docker containers or lambda functions. But that was a decision made on an evaluation of what we were doing. If we were doing something integrating MS Exchange or their AD federation for example, why would I not use C#?

'Just choose the most appropriate language for the task in-front of you'.....unfortunately that is not really an option for most Companies. At my clients place for example, the majority of devs are either Java (mostly) or Python ... and they are virtually all permies. So there is no chance management are going to say 'Go would be awesome for this ... let's build it with Go'. They are not going to cross train their devs for a 6 month Go project .. instead they will write it in Java / Python (or in our case c# going forward.)

When you say, there are a massive number of windows servers out there ... yeah I know that .. I helped to build some of the apps on them. When you say c# is not going anywhere .. I know that too. Again, I helped to build some of them. What I was asking is 'does it make any sense to choose c# for brand new projects that are intended to run on AWS and/or GCP'. I personally don't think it does.

As far as I can gather, the reason our management have decided to go with c# is because the current head of Dev for our Dept (based in another country) has experience in c#.

[ladymuck]

The beauty of building something in a language the permies don't have experience of is repeat business for tweaks and updates. If you do a good enough job of selling what you think is the most appropriate language for the job you could be in line to sign them up to a support contract too...

[eek]

As far as I can gather, the reason our management have decided to go with c# is because the current head of Dev for our Dept (based in another country) has experience in c#.

There is your answer

[DevUK]

If I had to take a stab at answering an incredibly vague question I would say yes, C# is a wise choice - especially when MAUI's (properly) rolled out.

That said, this is vague - it's like me saying "is a screwdriver the best tool for a job I need to do" without specifying any details of the job. I'm a C# dev, but I'm aware it's not always the most appropriate fit for everything.

[eek]

If I had to take a stab at answering an incredibly vague question I would say yes, C# is a wise choice - especially when MAUI's (properly) rolled out.

That said, this is vague - it's like me saying "is a screwdriver the best tool for a job I need to do" without specifying any details of the job. I'm a C# dev, but I'm aware it's not always the most appropriate fit for everything.

There is a similar question regarding - what cloud* should we use. To which the answer is the one you are already using as your staff will need to learn stuff to support the change and chances are they will simply up sticks and go somewhere else that that cloud is still being used.

* for cloud I mean AWS or Azure. No one sane is going to use the other options....

[d000hg]

'Just choose the most appropriate language for the task in-front of you'.....unfortunately that is not really an option for most Companies. At my clients place for example, the majority of devs are either Java (mostly) or Python ... and they are virtually all permies. So there is no chance management are going to say 'Go would be awesome for this ... let's build it with Go'. They are not going to cross train their devs for a 6 month Go project .. instead they will write it in Java / Python (or in our case c# going forward.)

If all your team are Java devs, Java is clearly the most appropriate language for the task. That's a big part of what "most appropriate" means.

[eek]

If all your team are Java devs, Java is clearly the most appropriate language for the task. That's a big part of what "most appropriate" means.

My 1 comment for that is if your team are Java devs and there are reasons why you may wish to change language (for Java is owned by Oracle and well it's Oracle) then C# may be a good compromise language that would be easier for people to learn than say python....

But yep - for most companies use the language your staff know even if it is vb.net

[d000hg]

My 1 comment for that is if your team are Java devs and there are reasons why you may wish to change language (for Java is owned by Oracle and well it's Oracle) then C# may be a good compromise language that would be easier for people to learn than say python....

But yep - for most companies use the language your staff know even if it is vb.net

But then also have a long-term strategy to modernise... without rushing into the decision based on a single project

[minestrone]

The wild west 90s when financials would order their army of Cobol devs to read Head First Java over the weekend as they were retooling and needed to deliver an online banking system in 4 months.

Those were special days.