× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I suspect that a large part of the "writing on the wall" is from the mass
of technical debt caused by neglect of their codebase over the years, not
the superiority of Node, PHP, Python, Ruby, etc.

I'd more put it on the neglect of the RPG community. Simply put, we don't
have enough RPG community to make the changes necessary for businesses to
succeed as fast as those adopting the newer languages. Sure you'll have
some success stories here and there with RPG, but the other langs have
serious advantages because of the community and module ecosystem (i.e
npmjs.com).


Brad>I think "lots of shops" is also an exaggeration. But also subjective.

Justin>I think that's kind of the work Aaron does, so he probably sees a
disproportionate number of those.

Bingo. Pardon me while I go finish off two more RPG-to-Node.js SOWs before
Saturday hits :-)


The biggest example is from Node4 to Node6 and the complete change of how
the db2 functions work.

The first rounds of the Node.js database connector were definitely
unfortunate, though the changes were definitely necessary. Corners are
being rounded and progress is being made.


And of course, the examples are terrible. Most, that aren't IBM, are just
copied from IBM with little or no change.

Yeah, help is needed in the docs front. We're really hoping some community
members can help on that front.


Aaron Bartell
IBM i hosting, starting at $157/month. litmis.com/spaces


On Fri, Mar 16, 2018 at 1:33 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

I didn't want to continue hijacking the other thread, but I wanted to
comment on this:

"Lots of shops are seeing the writing on the wall with RPG and are moving
away from it(n1) and selecting their next generation language. They could
go with the solid PHP, but then they'd be picking a language that's not on
the rise. They could go with Ruby (not extensively adopted on IBM i,
though very popular everywhere else). They could go with Python (another
solid general purpose language, and seeing more adoption on IBM i than
Ruby). Or they could go with the newer kid on the block that offers
something none of the others can, a single language for client and server."





I don't doubt your observation. I suspect that a large part of the
"writing on the wall" is from the mass of technical debt caused by neglect
of their codebase over the years, not the superiority of Node, PHP, Python,
Ruby, etc.

--
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: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.