Live data from Hacker News

Ask HN: Node vs. .NET Core (2024 edition)

news.ycombinator.com

11–20 of 53 posts

Re: Ask HN: Node vs. .NET Core (2024 edition)

#11
post #8

I know you're not asking about the personality behind the skills, but I'd sooner take a JS dev than a .NET one (even (and maybe especially) that Core runs on Linux), I'd even switch the entire stack to avoid having to deal with Windows talent. The ClickOps mentality in Microsoft-based ecosystems is astounding.

I'm a full stack Microsoft tech stack web dev since the days of asp classic. It's cool that the tech industry is big enough for all of us. I am not sure what the ClickOps mentality is, but I'm pretty sure I have it. Peace.

Re: Ask HN: Node vs. .NET Core (2024 edition)

#12
post #8

I know you're not asking about the personality behind the skills, but I'd sooner take a JS dev than a .NET one (even (and maybe especially) that Core runs on Linux), I'd even switch the entire stack to avoid having to deal with Windows talent. The ClickOps mentality in Microsoft-based ecosystems is astounding.

I'm a full stack Microsoft tech stack web dev since the days of asp classic. It's cool that the tech industry is big enough for all of us. I am not sure what the ClickOps mentality is, but I'm pretty sure I have it. Peace.

I think he's referring to all of the clicking required on Windows. For example, on Linux, I can create a project folder, files, etc. and open the project all from the terminal. On windows, I have to click into the file explorer, find the project folder, double click it to open it within the browser. So much clicking.

I admit, it's probably a skill issue. I've been using Linux distros for the last ~10 years, and am now working with .net codebases.

Re: Ask HN: Node vs. .NET Core (2024 edition)

#13

Earlier quoted context omitted.

I'm a full stack Microsoft tech stack web dev since the days of asp classic. It's cool that the tech industry is big enough for all of us. I am not sure what the ClickOps mentality is, but I'm pretty sure I have it. Peace.

I think he's referring to all of the clicking required on Windows. For example, on Linux, I can create a project folder, files, etc. and open the project all from the terminal. On windows, I have to click into the file explorer, find the project folder, double click it to open it within the browser. So much clicking. I admit, it's probably a skill issue. I've been using Linux distros for the last ~10 years, and am no…

I took it more as a dig at the way Microsoft offers its products. You want to spin up a new VM and deploy an app? Mindlessly click through these menus until you see a green checkmark.

It works well enough most of the time, but it also eliminates the need to think, so when something doesn't work as expected, ClickOps engineers are lost.

Re: Ask HN: Node vs. .NET Core (2024 edition)

#14
post #3

You use the tool best fit for your application. That's the answer to any language debate. That's how people make millions in profit even running just PHP ;)

Is that not the point of discussions like this? To talk about when each one makes more sense.

Re: Ask HN: Node vs. .NET Core (2024 edition)

#15

Earlier quoted context omitted.

I'm a full stack Microsoft tech stack web dev since the days of asp classic. It's cool that the tech industry is big enough for all of us. I am not sure what the ClickOps mentality is, but I'm pretty sure I have it. Peace.

I think he's referring to all of the clicking required on Windows. For example, on Linux, I can create a project folder, files, etc. and open the project all from the terminal. On windows, I have to click into the file explorer, find the project folder, double click it to open it within the browser. So much clicking. I admit, it's probably a skill issue. I've been using Linux distros for the last ~10 years, and am no…

with .NET Core you can do everything from the terminal and a text editor though

Re: Ask HN: Node vs. .NET Core (2024 edition)

#16

Either. It really depends on your use case. The developer experience is a lot better for .net, in my opinion, but it’s also expensive and usually requires windows (yes, Linux .net is completely possible). Microsoft invests heavily into building better, easier tooling from end to end. If you are an azure shop, it’s very easy to deploy. I haven’t looked at the latest benchmarks, but when I did, c# was a clear winner in…

> but it’s also expensive and usually requires windows

Can you please clarify what exactly is expensive and requires windows as far as .net is concerned?

Compared to 2016 the development and hosting experience for at least Linux (can't speak to Macs) has gone forward by a country mile. You can develop practically for free (no need to visual studio license since vs code exists) and target Linux environments during build so no need for windows server either.

Re: Ask HN: Node vs. .NET Core (2024 edition)

#17

Earlier quoted context omitted.

I'm a full stack Microsoft tech stack web dev since the days of asp classic. It's cool that the tech industry is big enough for all of us. I am not sure what the ClickOps mentality is, but I'm pretty sure I have it. Peace.

I think he's referring to all of the clicking required on Windows. For example, on Linux, I can create a project folder, files, etc. and open the project all from the terminal. On windows, I have to click into the file explorer, find the project folder, double click it to open it within the browser. So much clicking. I admit, it's probably a skill issue. I've been using Linux distros for the last ~10 years, and am no…

Precisely. The abstraction of knowledge is a cultural staple of that ecosystem. It's great and all, but you end up with developers who have no understanding of what is happening when they click "next next next next yes finish". On Linux, that understanding is a core pillar of the culture. Stark contrasts.

Re: Ask HN: Node vs. .NET Core (2024 edition)

#19

Either. It really depends on your use case. The developer experience is a lot better for .net, in my opinion, but it’s also expensive and usually requires windows (yes, Linux .net is completely possible). Microsoft invests heavily into building better, easier tooling from end to end. If you are an azure shop, it’s very easy to deploy. I haven’t looked at the latest benchmarks, but when I did, c# was a clear winner in…

> but it’s also expensive and usually requires windows Can you please clarify what exactly is expensive and requires windows as far as .net is concerned? Compared to 2016 the development and hosting experience for at least Linux (can't speak to Macs) has gone forward by a country mile. You can develop practically for free (no need to visual studio license since vs code exists) and target Linux environments during bui…

Yes, you can use vscode and rider. Rider isn’t free for companies and vscode has some free stuff, but Microsoft came out with a new extension for c# that requires a visual studio subscription. To me, this signals they will be directing the majority of their investment into this, rather than a free extension.

The experience isn’t as good in vscode (I haven’t used rider, but it costs money anyway, so still expensive) as it is in full fat visual studio.

At work, I use windows and full visual studio. At home, I use Linux and vscode.

Re: Ask HN: Node vs. .NET Core (2024 edition)

#20

Earlier quoted context omitted.

> but it’s also expensive and usually requires windows Can you please clarify what exactly is expensive and requires windows as far as .net is concerned? Compared to 2016 the development and hosting experience for at least Linux (can't speak to Macs) has gone forward by a country mile. You can develop practically for free (no need to visual studio license since vs code exists) and target Linux environments during bui…

Yes, you can use vscode and rider. Rider isn’t free for companies and vscode has some free stuff, but Microsoft came out with a new extension for c# that requires a visual studio subscription. To me, this signals they will be directing the majority of their investment into this, rather than a free extension. The experience isn’t as good in vscode (I haven’t used rider, but it costs money anyway, so still expensive) a…

You do not need "C# Dev Kit", it's nigh useless if you already used plain C# extension, which has the actual good bits you need.

Also, Rider is free if you apply for an OSS license (if you use it for FOSS), or have your company pay for it if you use it professionally.

Post reply on HN