I am a cloud application architect with 10 years' experience in software development in several languages, including Perl, Java and C#. I'm an Irishman living in Calgary, Canada. GitHub on @cubikca.
Location
Calgary, Canada
Education
BSc. Computing and Info Systems, Athabasca University
.NET 6 has syntactic sugar for all comers. For C# veterans, focus is on minimizing the amount of boilerplate code one has to write. For PHP developers, minimal APIs will look familiar to many. And these languages, as well as TS/JS have incredibly similar structure these days. It won't be that hard for a good developer to switch to .NET.
So why .NET 6? Because it is the most mature, most widely supported .NET. It runs on both ARM64 and x64 architectures. It has multiple IDEs for all three major desktop OSs. It works from front-end to back-end using Blazor WASM. But most importantly, it is fast and efficient. I expect to bring down our company's core count significantly next year by adopting .NET 6 and putting things in containers. I remember reading a case study on Microsoft's AD gateway servers moving from .NET to .NET Core, and cutting the core count in half.
Blazor WASM will really change the nature of the SPA. Being able to write in the same language from front-end to back-end really helps with development flow. Blazor WASM has first-class UI libraries, and integrates well with SignalR. Is Blazor any better than React? Maybe not. But it's certainly just as good, and now I don't need to learn another language.
Don't count Microsoft out. They've made huge strides in many aspects of development, and are rapidly bringing lots of people in. I'd be very surprised if Blazor WASM doesn't take off.
Knowing only one language and using it for both Frontend and backend is a big deal I have no doubt, my only problem with it is that I don't think it's going to make much difference in the real world.
You are a programmer for a reason which is to work. Most people learn coding because they want to get employed and use the skills and make money and in today's world no employer would sign a contract with you that says "you only use one language" never, at some point you are going to be learning something new.
I am a cloud application architect with 10 years' experience in software development in several languages, including Perl, Java and C#. I'm an Irishman living in Calgary, Canada. GitHub on @cubikca.
Location
Calgary, Canada
Education
BSc. Computing and Info Systems, Athabasca University
After many years and more languages than I can count on one hand, I'm not really interested in learning another. I have more than enough to keep me competitive :) For JS people, this is nothing new. For C#, though, it's a treat to be able to get away from ad hoc JS in the front-end.
My main reason for not wanting to learn another language is that I don't want to have to teach my team's developers another language. They are all good at C# and passable at JS. Research time is expensive. Making use of what you already have is better if reasonable.
.NET 6 has syntactic sugar for all comers. For C# veterans, focus is on minimizing the amount of boilerplate code one has to write. For PHP developers, minimal APIs will look familiar to many. And these languages, as well as TS/JS have incredibly similar structure these days. It won't be that hard for a good developer to switch to .NET.
So why .NET 6? Because it is the most mature, most widely supported .NET. It runs on both ARM64 and x64 architectures. It has multiple IDEs for all three major desktop OSs. It works from front-end to back-end using Blazor WASM. But most importantly, it is fast and efficient. I expect to bring down our company's core count significantly next year by adopting .NET 6 and putting things in containers. I remember reading a case study on Microsoft's AD gateway servers moving from .NET to .NET Core, and cutting the core count in half.
Blazor WASM will really change the nature of the SPA. Being able to write in the same language from front-end to back-end really helps with development flow. Blazor WASM has first-class UI libraries, and integrates well with SignalR. Is Blazor any better than React? Maybe not. But it's certainly just as good, and now I don't need to learn another language.
Don't count Microsoft out. They've made huge strides in many aspects of development, and are rapidly bringing lots of people in. I'd be very surprised if Blazor WASM doesn't take off.
True MSFT is making huge in-roads these days after stinking up the universe for eons.
I do feel C# Wasm is very strong and possible disrupter.
But Javascript is so large now, it will continue dominance for long time.
Now you get the point
Knowing only one language and using it for both Frontend and backend is a big deal I have no doubt, my only problem with it is that I don't think it's going to make much difference in the real world.
You are a programmer for a reason which is to work. Most people learn coding because they want to get employed and use the skills and make money and in today's world no employer would sign a contract with you that says "you only use one language" never, at some point you are going to be learning something new.
After many years and more languages than I can count on one hand, I'm not really interested in learning another. I have more than enough to keep me competitive :) For JS people, this is nothing new. For C#, though, it's a treat to be able to get away from ad hoc JS in the front-end.
My main reason for not wanting to learn another language is that I don't want to have to teach my team's developers another language. They are all good at C# and passable at JS. Research time is expensive. Making use of what you already have is better if reasonable.
Isomorphism is here now in at least 3 or 4 flavors. It is a nice thing to have front, back ends or microservices in same language.