Re: [IBMiOSS] Node code organization

I bit on the why not use....

So doing a little research (20 minutes' worth) it looks like these are node.js frameworks that others have come up with and all of them claim to have the world's attention, therefor use me.

Initial releases vary by framework but range from early last year to as many as 4 years ago. All of that gives me pause. The software architect in me says use the KISS method whenever possible.

We all know there are several immutable facts in software engineering. First is everything changes, so simple structures tend to support change better. Second is frameworks, design patterns, etc. change just like business requirements do. The developer that comes into the shop in 5 years will likely have never seen the neat new flashy framework you just picked as the "world standard", as VUE claims, since that mark tends to move very quickly. MVC has changed how much in the last 10 years?

Who cares what you pick as long as it is documented, the shop sets repeatable, and enforceable standards, and does not chase every neat new shiny object that is in vogue right now.


--
Jim Oberholtzer
Agile Technology Architects


-----Original Message-----
From: OpenSource [mailto:opensource-bounces@xxxxxxxxxxxx] On Behalf Of Justin Taylor
Sent: Friday, January 12, 2018 11:39 AM
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
Subject: Re: [IBMiOSS] Node code organization

I'm not familiar with the "component approach ".



-----Original Message-----
From: Kevin [mailto:kevin@xxxxxxxxxxxxxx]
Sent: Friday, January 12, 2018 2:10 AM
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
Subject: Re: [IBMiOSS] Node code organization

Do you really want a traditional MVC pattern? That’s generally considered a bit passé. If you are developing something new then I would go with the component approach (ala React, Angular 2 and beyond, Vue etc).


--
This is the IBMi Open Source Roundtable (OpenSource) mailing list To post a message email: OpenSource@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at https://archive.midrange.com/opensource.