|
I think you missed my point.--
Of course, there is a lot of old columnar RPG out there. Code that has
been running for decades.
I've stated my opinion on how short-sighted I think it is to leave the
code that way many time. But that is irrelevant to this thread.
This is a _new_ package being offered. I simply expressed disappointment
at _new_ stuff being put out in such an old format.
That is all.
Jon Paris
Jon.Paris@xxxxxxxxxxxxxx
On May 10, 2026, at 2:30 PM, Steve M <steven.meisinger@xxxxxxxxxxx>wrote:
myself.
Even as I am typing this I know it's a bad idea, but I can't stop
industry, like yourself, I think sometime forget that. It's columnar RPG,
There's a real world out there, Jon, and a lot of the leaders in our
not free. It's left-hand indicators and L1/LR logic. It's O-specs and not
PRTF. It's F-specs and not imbedded SQL. It's S36 legacy. It's PF/LF
(even fixed length F-Spec) and not DDL.
the backbone of systems today, RPG is no different. One must accept this
Just like the millions upon millions of COBOL out there that still runs
as fact; like it or not. As you put it, "hard to read" or not. That you,
or someone else might write it today, or not.
truth. Maybe you have the luxury of being selective to the best and
Client to client, company to company, I continue to encounter this
brightest of code - but a lot of us, I dare to say most of us, are slugging
it through legacy day in/day out. It's what got us here - it's what keeps
the platform relevant and even in use in most cases. Without it, they'd
fold it up and close it down.
positions, desires and beliefs, and even defiance. Sorry all, it is what
I know there is going to be a holy-war on this one; entrenched
it is. That's the system. Again, no different than COBOL, so I strongly
encourage we embrace it, support it, and even write in that fashion when
the client/company says, "we want our changes to look just like the rest
and not bounce back and forth old and new." Not every company has the
time, money, or more so the desire to want to enhance/upgrade/modernize.
That's okay - as long as they keep our platform alive we should encourage
them, support them, and assist them and not battle with them over a
meaningless hill to die upon; the hill of that's older code and you
(client/company) need to upgrade it. No, they don't. It's theirs to do as
they wish.
opposite, but to those who do I ask you this - why argue it at all? It's a
I am prepared for the onslaught of replies back at me arguing the
fact. It's out there. It's staying. If you don’t like to deal with it
wherever you are today then find a different shop to work and be happy.
But as long as your shop desires the old way, help them the absolute best
you can to make them be the absolute best they can be. For that, right
there, is what makes an IBM i developer different than any other language
or platform - we want the best for our client; not always ourselves.
Jon Paris
Steve
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Sent: Sunday, May 10, 2026 13:01native to the IBM i
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: TWOFA - A 2FA Two-Factor Authentication solution 100%
calcs in some cases.
Agreed but sad to see that so much of it is fixed form, though. Even the
fixed form calcs these days - so many years since I wrote any.
I know ... I'm getting old and cranky, but I really find it hard to read
wrote:
Jon Paris
Jon.Paris@xxxxxxxxxxxxxx
On May 10, 2026, at 1:15 PM, Richard Schoen <richard@xxxxxxxxxxxxxxxxx>
related questions.
This looks very interesting.
Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
----------------------------------------------------------------------
message: 1
date: Sun, 10 May 2026 12:53:14 +0800
from: Vengoal Chang <vengoal@xxxxxxxxx>
subject: TWOFA - A 2FA Two-Factor Authentication solution 100% native
to the IBM i
Please reference
https://github.com/vengoal/TWOFA
--
Best Regards,
Vengoal Chang
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-lhttps://archive.midrange.com/midrange-l.
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
related questions.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
list
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxxrelated questions.
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 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.
midrange.com
