81–90 of 124 posts
Earlier quoted context omitted.
Except it's a java copy. And java sucks
Have you ever actually written software professionally? I get strong teenage vibes from your comment history.
Earlier quoted context omitted.
If you're building Windows software, then you might find it easier to use the Windows-native stack. If you're not, then I'm not sure what the appeal would be. I work for a company in the former space. We have no intention of supporting nonWindows clients or nonWindows servers or even nonSQLServer DBs. It's not worth doing from a commercial perspective in our particular market. Consequently, it's C# and .NET.
I do all of my .NET work on a Mac and deploy to Linux -- both x64 and Arm64 -- on the daily.
Unfortunately, I agree that Microsoft was too late in realization that it is important to make it easier for developers and that they need to cater to the devs, instead of getting in their ways and making it harder for devs. The visual studio pro is still expensive (it should be FREE! community ed doesn't count) and still not as good as Jetbrain's Rider, which runs circle on VS. In fact, if MS had any sense, they should've bought Jetbrain just for Rider and scrap their bloated/slow visual studio, which only runs on Windows. MS needs to improve their tooling and also make VS for Linux if they want c# to be taken seriously for cross-platform dev. And stop changing the platforms and remove their absolute convoluted naming scheme. Why do we have .NET core which is now .NET 6, .NET framework is now supported and deprecated at the same time, desktop apps were written in WPF, and then UWP? and MAUI, and now is it called WinUI3? I have no idea because I can't keep track of changes anymore. One day it's called .net, who knows in few years it's going to be .azure, or whatever.
Earlier quoted context omitted.
But why can't you fork it and take it in the direction you want? The situation is literally no different from Python or Node or Ruby, the people running the most popular distribution could take it in a direction you don't like and the power you have (or the only option you have) is forking.
The development for a language like python happens entirely in public though, and is driven by consensus.
As a fullstack dev working with c#/.net backend and react frontend, I can say that c# is great, and I wished more projects would use it. Unfortunately, I agree that Microsoft was too late in realization that it is important to make it easier for developers and that they need to cater to the devs, instead of getting in their ways and making it harder for devs. The visual studio pro is still expensive (it should be FRE…
Why would you need pro? Also did you use VS with free extensions like Roslynator which significantly increase its refactor capabilities?
Earlier quoted context omitted.
This pattern exists in all languages. I’d argue more so in fragmented community driven projects/languages/tools. Except in the case of languages/tools like python, node, neovim etc. Everytime I touch one of these there is always a new better way of accessing DBs, making a web server, making a client side render, no a server side render, async library, configuration system, build system, runtime, GUI patterns etc.
There is a marked difference between a third party releasing some new library and obtaining (to some extent, demanding) community mindshare, without taking away anything, and the official platform maintainer suddenly replacing practically mandatory parts of what is perceived as the standard library. Javascript churn is fast, .Net churn is deep.
The only difference I see between both is that there is an authoritative opinion when it comes to .NET (Microsoft) while there is no authority figure when it comes to node/Javascript. Even the actual runtime, package manager, module resolution, build tools etc get forked and replaced but since there is no authority, everyone is like "lets wait and see who wins". While with a language like .NET (or Go for that matter) you know that whatever comes from Microsoft (or Google) is the authoritative answer and people are more likely to jump to it right away.
As a lifetime Linux user, I think it's obvious. A startup is about getting a product out to market as soon as possible, and hopefully as cheaply as possible, which can best be done with open and freely available tools. When I'm in the zone, my creativity is flowing, the last thing I need is to register on some website, or to purchase a license.
But it comes from the corporate world, was a Windows only product for years and (worse) was made by Microsoft, so hackers ignored it.
I only figured out how good it was because I started a job doing, yes, corporate/government it.
When I joined the .NET team in 2015, we were rounding out the first arc of the journey to be truly cross-platform, and June of 2016 released a 1.0. It was an absolute mess of a release, but it actually happened. You can bet your ass that "go after startups" was a part of the strategy - in my first team meeting we literally all read a blog post about how Go was picked over C# at Parse. I'm sure our execution of that s…
Having to argue with people about how well dotnet runs on Linux after having it deployed on Linux for 6-7 years sucks as hell