DEV Community

Discussion on: Is there a barrier to entry for .Net?

Collapse
tunaxor profile image
Angel Daniel Munoz Gonzalez • Edited on

I believe since .net core exists the technical barrier of entry is very low I'd take those 5 steps into 3'ish

  1. download |> install
  2. dotnet new console -o MyConsole
  3. dotnet run

I think it's more a mentality/opinion barrier the one .net needs to take down
many people I know these days still thinks like this

"oh, .net that's Microsoft no thanks"
"web frameworks in .net? you mean asp.net right?"
"yeah but is fake OSS"
".net GUI stacks are windows only, no thanks"

these points are strong for people looking on the outside but as far as I can see, we have projects like Giraffe, SAFE Stack, Uno Platform, Avalonia basically refute those opinions

I'd say in a couple of years people will realize that now that .net is cross platform they don't really need to rely on Microsoft to grow just as java projects don't really rely on Oracle to grow

Collapse
deciduously profile image
Ben Lovy

SAFE stack

Just want to say this is easily the best thing I accidentally discovered throughout last year, and I cannot wait until I have more time to learn more about it, as a non-dotnet user currently.

Collapse
luckynos7evin profile image
Andy Morrell (LuckyNoS7evin) Author

I agree with you, it’s not about the technicalities, it’s about the number of choices that come with something that’s almost 20 years old. It’s what people don’t know and assume, they do this off the old school ways that Microsoft has previously been known for and that they have been trying to shake for the last decade.

As you say it’s not down to Microsoft to bring in those new developers (although I’m sure they would like it). It’s down to veterans of .Net to maybe simplify down to the basic level and bring back the “Hello World” examples.

I like the 3 steps, could have gone that far but kept it at the same number as Python and Javascript.