The correct answer is Go
Ask HN: Node vs. .NET Core (2024 edition)
31–40 of 53 posts
Re: Ask HN: Node vs. .NET Core (2024 edition)
#32.net core is pretty cool. they even adopted a similar api to express if I remember well. Yeah it's fast too. faster than node. typed etc. but C# is a complicated language. and it keeps adding features. the have awesome tooling in .net world etc. but you know why javascript / node.js shines. JS is a simple language. of course lisps are simple i.e clojure. but only one other language comes close to the simplicity of ja…
The API adoption is in many ways the other way around - for example, a lot of JS frameworks are now mimicking HttpContext that ASP.NET and ASP.NET Core had for more than a decade. Ultimately, registering and routing endpoint is usually a smaller part of the project, but yes, the introduction of minimal API especially in combination with top-level statements is welcome
Otherwise, JS is an immediate productivity loss as you cannot trivially refactor the code, a lot of features exist to mimic strong typing (or you just use TypeScript instead), it cannot be directly compared. You use JS when it makes sense, when you have to. Pure back-end is not that situation.
Re: Ask HN: Node vs. .NET Core (2024 edition)
#33Ten years ago I stepped away from the Microsoft ecosystem, in large part due to said ecosystem drifting away from industry best practices at the time, and also a conservative development culture formed around this ecosystem that did not want to acknowledge the outside world. So if I were starting a new project eight years ago, .NET would've been one of the last technologies I would've picked, despite big love for C#.
When I was starting a new project a couple of years back, I went with .NET 6 and never looked back. The Core branch (and subsequent versions) fixed a lot of the issues I had with the original .NET Framework. Happily developing with VSCode on a Mac and deploying to ARM-based Linux instances in AWS. To the original question, the only right answer is you should pick what you know unless there is some overriding reason (e.g. performance). When building a backend API, I'd personally pick C# over JS all day.
Re: Ask HN: Node vs. .NET Core (2024 edition)
#34I 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.
Wait until you encounter how chromeos enterprise is managed.
Re: Ask HN: Node vs. .NET Core (2024 edition)
#35It's amazing how uninformed the comments are on the .NET ecosystem as of the time of this comment. The OP states this is intended as an update to a 2016 question, but the responses are largely stuck pre-2016, full of nonsense complaints that haven't been true for the better part of a decade (including imagined OS dependent lock-in, imagined lack of CLI based tools, and etc). The .NET Core variant doesn't even exist a…
> with no "Core" variant specifier existing anymore That's a good point and sorry for the mistake. In my defense I copied and pasted the title from the previous question and I don't know much about .NET in general.
>sorry for the mistake
You were asking the original question. It's reasonable to ask a question and not know the answer. We can, however, expect better of those who write in with answers.
Re: Ask HN: Node vs. .NET Core (2024 edition)
#36Earlier 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…
MS is sunsetting Visual Studio for Apple users in August and encouraging users to move over to VS Code.
Re: Ask HN: Node vs. .NET Core (2024 edition)
#37Earlier quoted context omitted.
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.
I'm having fun jumping into this conflict. Since I'm unabashedly on one side of the argument, I feel equipped and compelled to weigh in. The work my small team does is well documented, and when we execute our plans, we can click "next next etc." and everything works quite nicely. You're absolutely correct that I do not want to have an understanding of what is happening when I click next. I have a lot of other things that I need to understand. Humans for example do not have any "next" button so I spend a lot of time wrangling us. When the computer does what I think it out to do, then you're right I am not going to dig in. That's true. Inevitably I'm sometimes surprised when the computer doesn't do what I think it ought to, and I do have to dig in. Then I am perfectly happy to debug the situation. We figure out what's going on, fix it in the near term, update the documentation to address this in the long term, and then go back to clicking "next next etc." I call this productivity. I guess you could look down on me for not wanting to know things I am not getting paid to know. I look at it as saving my limited brain cells and attention for things I am getting paid to deal with.
Re: Ask HN: Node vs. .NET Core (2024 edition)
#38Earlier quoted context omitted.
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.
Create react app.
Re: Ask HN: Node vs. .NET Core (2024 edition)
#39I use .NET Core for AOT compiled binaries, which translate to trivial deployment workflows.
Re: Ask HN: Node vs. .NET Core (2024 edition)
#40Unless you use server-side rendering or JS-only dependency, in which case you do need Node.js, its usage cannot be justified as it is a massive downgrade in every way vs .NET (ASP.NET Core + EF Core/Dapper combo). Examples of major considerations are security vulnerabilities and dependency hell (both solved long ago in .NET), performance and memory footprint (the average expected difference in application code perfor…
A lot of people still have a negative opinion on .NET and C# where in fact it's probably the most productive combo and bang for your buck ever made when it comes to the quality of the actual framework, capabilities of the C# language (and to extent the other CLR languages like F#) and tooling. It checks all three boxes. There have been massive improvements in both support and new features after .NET Core came into being. Some people even say that they've been adding too much too fast recently. I don't know how it compares to Java and Go which seem to be the main competitors in that niche (not taking JS/Python/Ruby/PHP etc. into account), but I'd probably pick Go rather than Java myself if I had to abandon C#.