The "thin client" model connecting to a central unit is still always a winner for ERP style applications (be 5250, text, html/js, 3d, or whatever). Especially with the networking capabilities we have today, the security requirements, and economics and sustainability provided.
Especially one where you can update and swap a program live and that allow to debug a session centrally out a thousand of connected ones, live. For articulated business transaction
"Fat clients" are hard to manage technology, required now only for corner cases. So wasteful.
The html/js browser "thin client" nowadays provide a lot of capabilities (even serial connections to scales, 3d, websockets...).There is a lot of tech to leverage.Being trite, the thing lacking, is having a common stock in-the-OS "DDS 2.0" and "DSPF 2.0" , with decent functionality, because it would greatly increase TCO, numbers of VAR programming on it, providing solutions, manpower, this aiming for a "i"ntegrated turnkey solution, without losing oneself in infinite little streams...
On Tuesday, May 27, 2025 at 02:28:29 PM GMT+2, Justin Taylor <jtaylor.0ab@xxxxxxxxx> wrote:
I always thought WinForms worked well. Just put the apps on an SMB share,
and all that's required on the clients is the framework.
On Sun, May 25, 2025 at 8:55 PM Richard Schoen <richard@xxxxxxxxxxxxxxxxx>
wrote:
Winforms still works nicely. With .Net Core it's great because XCopy
deploy let's you deploy the app and .Net framework all together.
Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
midrange.com
