ekangal

Domain-Driven Design

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Companies like Twitter, LinkedIn, Uber, and many others use Node.js as their primary server technology or combine it with other languages.

7 Reasons for Startups to Choose ASP.NET Over Node.js

2. Node.js requires to mix & match languages to compensate for performance

<ol>
<li>There is no reason</li>
<li>There is no reason</li>
<li>There is no reason</li>
<li>There is no reason</li>
<li>There is no reason</li>
<li>There is no reason</li>
<li>There is no reason</li>
</ol>


<h3>1. .NET has better Performance</h3>
<p>Not always. But okay.</p>
<h3>2. Node.js requires to mix &amp; match languages to compensate for performance</h3>
<p>Not always.</p>
<h3>3. C# is an amazing language</h3>
<p>Yes. <a href="http://ASP.NET" target="_blank" rel="noopener nofollow">ASP.NET</a> (the framework) however, is not. The programmers often end up writing spaghetti. I miss the legacy code written in PHP. Legacy <a href="http://ASP.NET" target="_blank" rel="noopener nofollow">ASP.NET</a> code is a nightmare. Half of the time, you won’t even understand the error <a href="http://ASP.NET" target="_blank" rel="noopener nofollow">ASP.NET</a> throws at you. Straight 5  hours of debugging just to find out that old version of EF does not “always” resolve relations and you should have used <code>.include()</code>.</p>
<h3>4. Best tooling available</h3>
<p>What works in Visual Studio 2019 breaks in Visual Studio 2022. Why? Because the IDE controls the solution and csproj file and hardcodes its own stuff into it.</p>
<h3>5. Easier built-in development loop</h3>
<p>Which is not always best in all cases. It limits you to a specific deployment strategy.</p>
<h3>6. Stable ecosystem</h3>
<p>Yes.</p>
<h3>7. Compliance, privacy, and security</h3>
<p>Security is a myth. Moreover npm gives security warnings during installation which you won’t get in NuGet. A false hope of being secure is worse than knowing you have no security at all.</p>


<p>Are you sure you don’t mean the other way around? Because as far as I know, Node.js is the cool kid on the block and <a href="http://ASP.NET" target="_blank" rel="noopener nofollow">ASP.NET</a> is that weird uncle who still uses AOL.</p>


<p>Interesting article taking the “less popular approach” for writing web services choosing <a href="http://ASP.NET" target="_blank" rel="noopener nofollow">ASP.NET</a> over Node. I’m not convinced but I’ll look slightly better on startups that will make that choice.</p>
