Microsoft should really change the name .net core to something else.
Too much history
Ask HN: Why is .NET not popular with startups?
91–99 of 99 posts
Re: Ask HN: Why is .NET not popular with startups?
#92Earlier quoted context omitted.
Care to elaborate? You already throw around blanket statements, it's not enough to just say "yes". What's your rationale?
He has no rationale. Doubt he even knows the scale at which MS' tech stack is used, especially outside of the USA's hipster bubbles.
Re: Ask HN: Why is .NET not popular with startups?
#93Earlier quoted context omitted.
He has no rationale. Doubt he even knows the scale at which MS' tech stack is used, especially outside of the USA's hipster bubbles.
Those "hipster bubbles" are the areas where most tech innovation is happening. Nobody is saying that insurance companies aren't using .NET.
"Boring" industries like insurance might not seem innovative on the outside because their members aren't blogging and twattering about it constantly. One of my clients does catastrophe modeling, and uses both Python and .NET (F#)...but it's probably not going to be something on your radar. But guess what, they're raking in the dough while actually being innovative, yet you're here on HN claiming they're not proper engineers.
Best of luck to you.
Re: Ask HN: Why is .NET not popular with startups?
#94Re: Ask HN: Why is .NET not popular with startups?
#95There has always been a dark horse OS within .NET its called F#. But what is sad about the state of the average C# dev is that when I ask them about their opinions on F#, they always respond with a "whats F#?" That's the problem with most .NET developers. They were fed straight from the MS spoon with blinders on, and never wondered what is out there. But to label oneself as a "I'm a .NET dev", and yet you don't know…
Why F# syntax is not c like? That would have increased the adoption
Re: Ask HN: Why is .NET not popular with startups?
#96There has always been a dark horse OS within .NET its called F#. But what is sad about the state of the average C# dev is that when I ask them about their opinions on F#, they always respond with a "whats F#?" That's the problem with most .NET developers. They were fed straight from the MS spoon with blinders on, and never wondered what is out there. But to label oneself as a "I'm a .NET dev", and yet you don't know…
F# isn't an OS. And it hasn't always been around, it's much newer than .NET.
> But what is sad about the state of the average C# dev is that when I ask them about their opinions on F#, they always respond with a "whats F#?"
And, so what? F# isn't C#. Why should a “C# dev” be expected to know F#.
> That's the problem with most .NET developers. They were fed straight from the MS spoon with blinders on, and never wondered what is out there.
F# is from MS and it's not exactly hidden by them. But why should a “.NET dev” be anything other than someone who has sufficient knowledge and proficiency with programming with the .NET framework, irrespective of whether it's all in VB.Net or whether they are a ployglot?
Re: Ask HN: Why is .NET not popular with startups?
#97People have rightly mentioned the cost and vendor lock-in issues. The other problem is that - for whatever reason - good engineers simply want nothing to do with the Microsoft ecosystem. In this market, they have other options. So tying your infrastructure to .NET means limiting your hiring pool to mostly 9-to-5er enterprise developers who tend to fix problems by asking Microsoft to sell them the solution. Not exactl…
Re: Ask HN: Why is .NET not popular with startups?
#98Earlier quoted context omitted.
He has no rationale. Doubt he even knows the scale at which MS' tech stack is used, especially outside of the USA's hipster bubbles.
Those "hipster bubbles" are the areas where most tech innovation is happening. Nobody is saying that insurance companies aren't using .NET.
I can see why you would think that when that's the only place in which you are looking.
Re: Ask HN: Why is .NET not popular with startups?
#99We use .NET Core at Namely and we are generally super happy with it. About half of our new services are in C# with .NET core using protobufs/gRPC in Linux Docker containers on Kubernetes talking to Postgres, Redis, and Kafka; the other half are Go but otherwise same stack. That’s all free/open source stuff. .NET Core is super fast and has a generally pretty small memory footprint. It works great with our ELK stack mo…
I am curious: Why is your other half of your services in Go ? If you are happy with .Net ?