Re: Node.js vs. MS .Net Web Application Development

Hmm... At least to the client side comment I would think they are all using HTML/CSS/Javascript for client side development so not sure your statement on that one rings true.

Most of it comes down to religion, boredom and age.......

Younger developers groove on what they perceive as new: Developing client and server with Javascript.

Bored programmers decided it would be cool to create Javascript based server-side apps so as not to learn more than un-typed javascript.

RPG, .Net, Java, PHP or other programmers decided to pray to a new language of choice.

Developing on any of these is always going to be up for debate. Which is easier, which is faster, which is more hip and less legacy.

That's as deep as my commentary goes on this one except to say:

.Net :-)

Regards,

Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx
www.rjssoftware.com
Visit me on: Twitter | LinkedIn

------------------------------

message: 3
date: Mon, 12 Oct 2015 10:25:07 -0600
from: Nathan Andelin <nandelin@xxxxxxxxx>
subject: [WEB400] Node.js vs. MS .Net Web Application Development

Over the weekend I was searching for Node.js vs. .Net performance
benchmarks. A couple relevant comparisons surfaced. A number of blogs also
surfaced which debated the merits of switching from MS .Net to Node.js.

Some of the blogs authors were highly experienced developers, who had built
careers spanning up to 15 years based .Net mastery, who were switching to
Node.js.

My personal bias tends to support language environments which run on IBM i
on Power. I personally don't have a stake with either Node.js or MS .Net.
But I'm interested in seeing some discussion about switching Web
application development from MS .Net to Node.js.

I'd like to begin by passing along some of the rationale which originates
from experienced .Net developers.

One relevant benchmark entailed a test which "posted" a small JSON file to
Node.js and .Net web services which simply returned the same file back to
the client.

The Node.js version implemented its standard HTTP interface, while the .Net
version implemented a Web API interface instead of the more common/complex
IIS <==> Aspx.Net interface. The Node.js version had somewhat higher I/O
throughput and approximately 50% lower CPU utilization on Windows servers.

The growing popularity of Node.js for new application development in
organizations was cited as a preference over maintaining legacy .Net
applications. Comparisons were made between legacy .Net and COBOL code
bases.

.Net complexity was cited, especially in regards to major paradigm shifts
which have occurred in the .Net web application framework. .Net no longer
provides a homogeneous framework for web application development. There
have been major shifts from PHP-like Active Server Pages, to Web Forms, to
MVC, to Web API, and a wide-range of of third-party add-ons.

Regarding complexity, I recall one article titled Eight was to Manage User
State in .Net Web Applications.

.Net developer IDE's were viewed as "heavy", especially Visual Studio - and
having high license fees per developer for team development. There is a
slight shift to light-weight server-side development IDE's.

.Net frameworks are geared toward developing heavily server-centric web
applications, while there is a growing trend for making Web applications
more client-centric.