Language isn't important unless it is business critical. And successful businesses are scarce.
The Case for C# and .NET
201–210 of 376 posts
Re: The Case for C# and .NET
#202This thread shows there is still a large amount of FUD around .NET and it’s community. Folks here still think it’s Windows-only and comparable to Java. Yet latest TechEmpower benchmarks shows .net running on Linux and being faster than Go, Python, Node, and Rust.
That's not true atm.
At time of writing (TechEmpower 21) Rust frameworks have top 3 out ouf 5 slots (#2, #3 and #5) in composite rankings. https://www.techempower.com/benchmarks/#section=data-r21&tes...
Which goes to show, benchmarks change and depend on use case. And Rust is very competitive (in league with C/C++).
Re: The Case for C# and .NET
#203Earlier quoted context omitted.
Have you actually tried Blazor ? Just the schism between WASM and Server and the feature matrix there, and generally shit quality of early stage Microsoft product - I wouldn't touch it with a 10 foot pole, likewise for MAUI - I've seen coworkers prototype both for some greenfield projects in last month or two and both projects gave up on it because it just isn't there yet for mainstream development. I mean .NET core…
I've tried Blazor. I built and deployed 3 apps for clients over the last 3 years while consulting and was able to deliver the projects for 33% what it would have cost to deliver them with react or angular. Clients have been very happy with the results. Then I built my own startup with it, and we have a solution that 3 devs have been working on for 2 years. I can't recommend Blazor enough. I love it. I have run into a…
That's part of my problem with it - from what I see they are pushing two independent tech stacks (WASM and dynamic server rendering/JS updates) under the same name - but the APIs underneath and the architecture is very different.
Re: The Case for C# and .NET
#204I also think that C# and .NET are awesome. Especially latest releases dotnet 6 and upcoming 7 have a ton of new things to be even more productive. I like the fact, that you can develop command line apps, Web APIs, Desktop Apps and smartphone apps all with the same toolset, including the fact that deployment is possible on nearly every major platform for every major platform (except iOS and macOS Apps, as always only…
> I don't like Visual Studio as IDE, but VS Code is an acceptable alternative tool, although I personally prefer the non-free JetBrains Rider. I've used Visual Studio for 20 years now, and while the tooling has come a long way, I'm starting to feel like MS and the community are abandoning it for VS Code. I don't mind VS code, but unfortunately the stack I'm working in (Dynamics 365) requires plugins for Visual Studio…
I see they move in VSCode direction with tools like Power Platform CLI [1], power platform tools extension [2]. PCF (PowerAps Component framework) enabling to develop UI components in frontend framework-of-choice... however none of that is available (yet?) for On-Premise deployment so we're 2nd class citizens. Because of that, haven't been able to play with this and try out so don't know how far that tooling goes.
As a platform, I really like it. Sane, consistent (except some very early stuff there), the backend extensibility - thumbs up for that.
[1] https://docs.microsoft.com/en-us/power-platform/developer/cl...
[2] https://marketplace.visualstudio.com/items?itemName=microsof...
Re: The Case for C# and .NET
#205Earlier quoted context omitted.
Curious, what is it with Microsoft that makes it so poisonous for you that you won't touch anything they make with a ten foot pole? As an example, I'd say Facebook (Meta) is a way more toxic company but I've never heard of a developer have moral arguments against using React
I'm using Linux for 20 years, and witnessing what Microsoft is doing for more than 25. Being openly hostile towards Linux and plotting ways to lock it out of hardware platforms and tech ecosystems is enough of a motivation for me. It's not only their stance against Linux only, but everything competing with them. I believe hardware and software should be open and platforms shall compete openly. I don't use any vendor…
I'm curious, what do you have against LLVM? I'm sure it supports fewer backends than GCC, no surprise given their relative ages, but it's still got quite a few and it's open enough that it has documented support for adding new backends.
Re: The Case for C# and .NET
#206Earlier quoted context omitted.
What part of the .NET SDK isn't supported on Linux?
I think they are referring to visual studio support which doesn’t exist on linux. But if you wanna use VSCode or Rider then the support is 100%
Re: The Case for C# and .NET
#207Earlier quoted context omitted.
How are collections in C# worse than in Go? In C# you have LINQ, in Go you're writing for loops around array slices.
Maybe I was using it wrong? As I recall, "the usual" APIs present in most other OO languages were not available when I tried to help a friend with a project 3 montjs ago.
Most languages copy c#
Re: The Case for C# and .NET
#208The article makes a case against using Node.js but doesn't bother to provide a comparison of C# and its actual competitors: Java and Go.
I understand that 90% of Kotlin's audience is mobile devs and server-side Kotlin is rare, but as a .NET developer, a few years ago I did a small production Spring Boot webservice in Kotlin and the experience was really good.
Re: The Case for C# and .NET
#209Re: The Case for C# and .NET
#210Earlier quoted context omitted.
I use Rider on my Ubuntu machine and the dev experience for me, is even better than using VS2022 on Windows.
Quoted post unavailable.
Perhaps not truly free, but within reach for most people.
Also, the EAP is $0 (although it's pre-release and not always guaranteed to be available)