Ask HN: Node vs. .NET Core (2024 edition) • Hacker News Board

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

#51

Post by HumanOstrich » Tue, Apr 16, 2024, 8:43 PM UTC

dzonga wrote: post #29

pier25 wrote: post #26

Earlier quoted context omitted.

JS kinda sucks for anything complex though. That's the reason almost everyone has switched to TS and then you lose the malleability and simplicity of JS. At which point why not just use C#?

and why are you using TS to begin with ? and yes I agree if you're gonna jump on the typescript wagon, why not use C# etc. types are good ? yeah ... but to a limit. Tests make for better programs than types. Using values too instead of mutations etc. Rich Hickey - makes a good point in his the Value of Values talk. and another point -- someone is gonna mention about node.js libraries being abandoned etc -- I don't kn…

That's because Express has been seriously neglected for the past 10 years. That's why it's still version 4. I think you still have to hack in basic support for async handlers.

Performance is bad. Bad as in all the other frameworks use it as a baseline for their benchmarks lol.

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

#52

Post by amarkdown » Fri, Apr 19, 2024, 12:40 PM UTC

Just like the bias against C# we all share, in 2024 we should talk about something new when discussing Node.js. I think Bun should also be part of this conversation. Bun is designed to improve the Developer Experience (DX) in the JavaScript world.

In 2024, if you use TypeScript (strict mode) with Bun, Biome, and tRPC, you can get excellent types, a great toolchain, and all configurations become straightforward. Dependency installation is very fast, and you no longer need to worry about package managers; packaging and compilation are also simplified. Moreover, in the software industry downturn of 2024, we're most likely all full-stack developers. We can't escape the fact that JavaScript runs in the browser, and with the above setup, you can effectively share types between the front and back end.

Regarding database types, there's also Prisma or Drizzle (yes, the JavaScript world is always full of wonderful new things). They allow for the convenient creation of fully typed models, and we can easily use 'import type' to share types with the frontend.

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

#53

Post by amarkdown » Fri, Apr 19, 2024, 12:51 PM UTC

amarkdown wrote: post #52

Just like the bias against C# we all share, in 2024 we should talk about something new when discussing Node.js. I think Bun should also be part of this conversation. Bun is designed to improve the Developer Experience (DX) in the JavaScript world. In 2024, if you use TypeScript (strict mode) with Bun, Biome, and tRPC, you can get excellent types, a great toolchain, and all configurations become straightforward. Depen…

Addition: Learning a language is simple, but becoming skilled in using it and understanding its common ecosystem takes a long time, usually between 6 to 18 months for most people. The ecosystem of front-end applications overlaps significantly with Node.js, which is undeniable. No matter how much you like C#, you can't avoid initiating a front-end project that includes Node.js. Therefore, you end up managing both Node.js and C# ecosystems. Don't mention Blazor to me; in reality, most applications still use React, Angular, or Vue.