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

Nathan

you are right,

we are not talking about "religion" but different paradigms.

If you develop binary APP's for iOS or Android they really
don't know the server language that serves the data.

The same goes for EXT JS - it is "stand alone" APP's where
you may put any server programmed in any language "behind".

On Tue, Oct 13, 2015 at 12:12 AM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

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.

My understanding is that there is a shift from using drag-and-drop screen
designers which generate "page" layouts. There is movement from using
server-side interfaces and generators which "merge" database "objects" with
page "objects", and stream the results to clients.

The trend is to perform those types of merges by using client-side
frameworks. The work on the server is reduced to processing requests for
JSON objects.

Responsive UI design is replacing "layouts" generated by screen designers.
Screen design paired with database binding has been the bedrock of
Microsoft's application design philosophy since the days of Visual Basic.

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

I'd prefer that the term "religion" not be used in a negative context. I
define "religion" as moral behavior and practices designed to bring oneself
into alignment with God, based on scripture, prophetic counsel, spiritual
manifestations, etc.

You seem to be referring to "protecting" personal interests. And I would
agree that is what drives most people's decisions.

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.

The interests of developers should be included in the mix. But so should
the interest of users and system administrators, and operations which
outlast the interests (and whims) of developers.

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 :-)

Okay, thanks for your input.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.