News for hackers. Stuff that matters.
Re:COBOL programmers answer call by triska on Friday April 10, 2020 @06:19PM (#22837896)
COBOL can be a real pleasure to use.

For instance, it allows programmers to quickly create user interfaces by declaratively describing them, in a so called SCREEN SECTION.

The resulting interfaces are very efficient for text entry, and allow users to quickly get a lot of work done. The interaction is so much more efficient than what we are used to with current technologies that it can barely be described or thought about in today's terms.

Regarding the underlying theme of legacy systems, here is an interesting presentation by Jonathan Blow, citing various examples of earlier civilizations losing access to technologies they once had:

https://www.youtube.com/watch?v=pW-SOdj4Kkk

I think in terms of user interfaces, we are on a downward path in several important ways, and I highly recommend checking out earlier technologies that were in many ways an improvement over what we are working with today.

Re:COBOL programmers answer call by tynpeddler on Friday April 10, 2020 @08:15PM (#22838688)
At one of my previous jobs, I was responsible for designing and building a webapp to replace a high speed data entry system that had been written in cobol that was used to input large legal documents (several thousand lines of data in some cases). We had two objectives, data entry had to be as fast or faster than the old system and the training time on the new system had to be faster.

We blew both objectives out of the water. Training time went from 3-6 months to about 2 weeks. We had a variety of modern UI concepts like modals, drop downs and well behaved tables that dramatically simplified the work flow. We also had a full suite of user defined hotkeys, as well as a smart templating system that allowed users to redefine the screen layout on a per use case basis (the screen would be reconfigured based on what customer the user was entering data for example).

For performance, cobol typically requires a server round trip every time the screen changes. We simply cached the data client side and could paginate so quickly that it actually caused a usage problem because users were not mentally registering the page change. The initial screen load took slightly longer compared to the cobol system, but the cobol system required 40 screens for its workflow whereas our system could do everything on a single screen.

I guess my point is that modern systems are capable of much better performance and user ergonomics than cobol systems. We have a lot more flexibility in how UI's are presented that let us design really intuitive workflows. The flexibility also lets us tune our data flow patterns to maximize performance. But most modern development processes do not have this kind of maniacal focus. Systems don't perform because most product owners don't really care that much at the end of the day. Once you care enough, anything's possible.

Re:COBOL programmers answer call by aetherspawn on Friday April 10, 2020 @09:31PM (#22839031)
In my last job we wrote a front-end that ran the COBOL and streamed the presentation information to the client over a websocket. It allowed them to use 30+mil LOC of existing apps.

The resulting webapps were made automatically responsive for the web and could be run anywhere - desktop, tablets, phones and apps could open tabs that invoked other apps for multitasking. We also added some custom commands to the COBOL so that they could invoke web based graphs, reporting, printing, pdf generation, etc. The client supported native typeahead, so the web apps behaved very much like desktop apps whereby pressing a number of shortcuts simultaneously resulted in them being played in order and overcoming any latency. This made the apps completely superior to normal web apps for their application (i.e. POS, ERP systems).

The utility that COBOL provided, coupled with a modern web based runtime written in React, was remarkable. Truly a hybrid of both the best parts. When I left, they were working on wrapping the React webapp into a React Native app.

Re:COBOL programmers answer call by murphy214 on Saturday April 11, 2020 @06:12AM (#22840846)
For "presentation information"are you saying you just stream back the normal text on the screen (for that piece of information in the COBOL app) and then parse it into some sort of API?

I have no idea about COBOL at all but I've done something like this before with a client mainframe scripting/macro language, it was not fun. Basically I had to hard code a bunch of key inputs to get the information screen I needed finally read that screen back out in plain text and parsing that into some sort of structure. It was a mess but worked for what it required at the time.

Re:COBOL programmers answer call by aetherspawn on Saturday April 11, 2020 @07:37AM (#22841131)
Things like buttons and windows are streamed across.
Re:COBOL programmers answer call by nulbyte on Friday April 10, 2020 @09:03PM (#22838918)
> For performance, cobol typically requires a server round trip every time the screen changes.

Round trips aren't the problem. Waiting for IO is. CICS solves this by not waiting for IO. It dumps the screen and moves on. Then it becomes the terminal's responsibility to wake CICS up with an attention key. If a front-end application is stuck waiting for terminal input, it's written wrong.

Re:COBOL programmers answer call by earthboundkid on Friday April 10, 2020 @11:29PM (#22839458)
> Once you care enough, anything's possible.

People should bring back sigs, so that can become a meme.

Re:COBOL programmers answer call by nivethan on Tuesday April 14, 2020 @11:06AM (#22866871)
Hi, I'm curious how you designed the app? Did you use the existing application as a base and try to duplicate it in the web or was it a completely different beast? Do you have any book recommendations or even blog posts for how to upgrade legacy UI? It's a topic I'd love to dive more into and I don't hear as much success stories as I would like.
Re:COBOL programmers answer call by fareesh on Friday April 10, 2020 @08:45PM (#22838809)
How long did it take? What frameworks/libraries did you use?
Re:COBOL programmers answer call by tynpeddler on Friday April 10, 2020 @09:15PM (#22838978)
We used Angular 1. Took about 2 years, but it was just me for about half that time and we were all learning js and the web ecosystem. The new system had been prototyped a few years earlier using java swing. That really helped nail down the design requirements.
Re:COBOL programmers answer call by momofarm on Friday April 10, 2020 @10:08PM (#22839163)
Has this meet expected budget? Compare to continue maintain existing cobol system?
Re:COBOL programmers answer call by gumby on Friday April 10, 2020 @07:13PM (#22838333)
> For instance, it allows programmers to quickly create user interfaces by declaratively describing them, in a so called SCREEN SECTION.

By the way if it seems odd to have I/O like this in your language:* this reflects the architecture of mainframes; because the CPU was so important, I/O was managed by external devices (typically themselves a cabinet of electronics, at a time when the CPU took up two or three cabinets itself). You'd write essentially a small program describing what IO you wanted and then let the IO channel controller be busy dealing with minutiae like dealing with the tape drive motor or input from terminals.

So the language would set up data to be slapped to a terminal (this would have been a decade or more after COBOL was written, once terminals with screens were available), which the channel controller would send to the appropriate terminal. It would then deal with input and once all was ready, tell the CPU that it had a bunch of input ready.

Terminals like the 3270 were even half duplex so would process the input and then send it off as a block, to make the channel controllers more efficient!

In the ARPAnet of the 1970s, the ITS PDP-10s and -20s took this further with a protocol called SUPDUP (super duper) which allowed this kind of processing to be done on a remote machine when logging in over the net (as we would do today with ssh). So you could log into a remote machine and run EMACS, and while you were editing a remote file with a remote editor all the screen updating would be done by your local computer! Even the CADR lisp machines supported this protocol!

* At the time not doing IO through the language itself was considered oddball. I seem to recall a line in the original K&R where they described C's I/O and made an aside, '("What, I have to call a function to do I/O?")'

Re:COBOL programmers answer call by rbanffy on Friday April 10, 2020 @08:33PM (#22838759)
It's quite clever, actually. Offloading specialized work to autonomous subsystems allows the CPU to run your code better than it would if the CPU also had to deal with reading from disk or assembling packets for the network. A modern mainframe has tons of such systems and that's what allows them to process volumes of transactions that PC-based servers of the same price range can't.

In fact, our PCs are like that because they had to be cheap and the cheapest way is to burden the CPU with all work.

Re:COBOL programmers answer call by gumby on Friday April 10, 2020 @08:52PM (#22838850)
Actually I’d disagree a bit with your last sentence. Handling io interrupts in the kernel was a property of cheap machines like minicomputers that you could buy for a few hundred $k or less. You typically couldn’t afford extra channel controllers on cheap machines like that. Hence Unix’s I/O architecture was driven by the constraints of the PDP-7. Multics has a standard io controller architecture.

PCs of course had the same issue — down to the cpu controlling the speed of disk rotation! But a modern PC has an I/O system more complex than the mainframes of old, with network interfaces that do checksum processing, handling retransmission and packet reassembly etc, just DMAing the result. Disk drives, whether spinning or SSD have a simple, block interface unrelated to what the storage device is doing, etc. I think this is all as it should be, though I personally consider the Unix IO model grossly antiquated.

Re:COBOL programmers answer call by DonHopkins on Saturday April 11, 2020 @05:01AM (#22840542)
If /dev/zero is an infinite source of zeros, then why doesn't the minor device number specify which byte to use? Then you could make character special file /dev/seven that was an infinite source of beeps! There have been so many times I needed that.
Re:COBOL programmers answer call by rbanffy on Saturday April 11, 2020 @07:07AM (#22841049)
Great idea! Also, for when you need some paper, you can pipe /dev/twelve to your printer.

We should propose a kernel patch for this next April.

Extra credit if we get it rolled into POSIX.

Re:COBOL programmers answer call by gumby on Saturday April 11, 2020 @12:26PM (#22842467)
Star Wars is more advanced and had this. How do you think R2D2 wasn’t cut from that film? He had an advanced case of Tourette’s so everything had to be beeped out.

Imagine if they’d run out of beeps during filming!

Re:COBOL programmers answer call by zozbot234 on Friday April 10, 2020 @09:20PM (#22839000)
These days, the "autonomous subsystem" is a microcontroller at the other end of a USB, SATA or PCI bus. Modern network cards also need to perform most of their packet-assembly operations on device and not in the kernel, or they would never reach their advertised max bandwidth.
Re:COBOL programmers answer call by rbanffy on Saturday April 11, 2020 @04:48AM (#22840498)
Those controllers are still designed prioritizing cost over performance most of the time.
Re:COBOL programmers answer call by gumby on Saturday April 11, 2020 @12:28PM (#22842476)
Well it’s system cost — the controllers take the high frequency interrupts, not the cpu.

As for BOM...a few years ago we designed a big serial board (industrial control) and found it was much cheaper to buy AVR cpus and use just the onboard UARTs than to buy UART chips.

Re:COBOL programmers answer call by macintux on Friday April 10, 2020 @08:26PM (#22838743)
Almost 25 years ago I took a TCP/IP class in Chicago that turned out to be a waste of my time, because it primarily dealt with clients like ftp, telnet, etc that I was already quite familiar with.

However, the rest of the students were mainframe guys, so it was an interesting few days. My (Solaris, Linux) world seemed incomprehensible to them, and vice versa, but it was nice to get a glimpse into how the other half lived. Finding experienced computer people who’d never used ftp was quite surprising.

Re:COBOL programmers answer call by BiteCode_dev on Saturday April 11, 2020 @02:00AM (#22839906)
Separating the IO from the rest of the program is always a good practice, that we keep rediscovering.

E.G:

- UI in React are trying to be just rendering functions with one input and one output. Even more so with hooks.

- in python, there is a new trend of providing "Sans I/O" (https://sans-io.readthedocs.io/), and async/await are not just keywords, but a generic protocol created to delegate I/O to something from outside your code.

It's interesting to see that on very old systems, even the hardware was organized that way.

Re:COBOL programmers answer call by derefr on Friday April 10, 2020 @11:28PM (#22839455)
Oddly, that reminds me a lot of early game consoles! You'd just set up some sprite registers, or send some commands to music sequencer hardware, and then those would go on and persistently do things on their own while the CPU got on with the "business logic" of running a game.

It's funny how it was the systems in the middle (minicomputers, like the PDP-11 where C originated) that did everything on the CPU, whereas the systems on the high end (mainframes) and low end (microcomputers) both split the work out, for different reasons: mainframes pushed IO out to independent coprocessors for multitenant IOPS parallelism (can't make any progress if the CPU gets an IO interrupt every cycle); while early microcomputers pushed IO out to independent coprocessors to retain the "feeling" of real-time responsivity in the face of an extremely weak CPU!

Re:COBOL programmers answer call by gumby on Saturday April 11, 2020 @01:26AM (#22839792)
I never thought of a sprite chip this way but your message makes me think I should have. A sprite chip was a kind of coprocessor like an external floating point unit or a GPU.
Re:COBOL programmers answer call by a1369209993 on Saturday April 11, 2020 @04:18AM (#22840387)
A sprite chip literally is a GPU [Graphics Processing Unit], just for 2d graphics (sprites,tiles,color palettes,etc) rather than 3d (vertex,triangles,fragment shading,etc).
Re:COBOL programmers answer call by derefr on Saturday April 11, 2020 @11:33AM (#22842189)
Mind you, a PPU is specifically, in most cases, more like an iGPU (integrated GPU, like Intel's on-CPU graphics.) Most of the PPU chip designs tended to share a memory (both physically and in address-space terms) with the CPU, such that the CPU would write directly to that memory, and then the PPU would read back from that memory. (This was when the PPU had memory at all; often they were pixel-at-a-time affairs, doing just-in-time sprite-tile lookups from the ROM pointed to by their sprite-attribute registers.)

Most things we call "coprocessors", on the other hand, were a bit different: they had their own on-board or isolated-bus memory, which only they could read/write to, and so the CPU would interact with them with "commands" put on a dedicated command bus for that coprocessor. Most sound chips (down to the simplest Programmable Interval Timer, but up to fancy chips like the SNES's SPC700) were like this; as were storage controllers like memory cards and the PSX's CD drive.

Re:COBOL programmers answer call by gumby on Saturday April 11, 2020 @12:31PM (#22842491)
Literally true.

I was thinking of the GPUs we had in those days which were often a couple of VME cards or even a small cardcage, but you’re right: that physical distinction isn’t really relevant.

Re:COBOL programmers answer call by goatinaboat on Saturday April 11, 2020 @02:43AM (#22840045)
In the Amiga it was called the Copper which was an abbreviation of co-processor.
Re:COBOL programmers answer call by DonHopkins on Saturday April 11, 2020 @04:47AM (#22840493)
SUPDUP and EMACS supported "line saving", so Emacs could send a control code to tell a SUPDUP terminal to save lines of text in off-screen buffers, and restore them to the screen, so EMACS only had to send each line one time, and the SUPDUP terminal could quickly repaint the screen as you scrolled up and down through a buffer.

Here's my Apple ][ FORTH implementation of SUPDUP with line saving (%TDSAV, %TDRES), which saved lines in the expansion ram card.

https://donhopkins.com/home/archive/forth/supdup.f

Re:COBOL programmers answer call by ffhhj on Friday April 10, 2020 @08:52PM (#22838844)
Now in HTML5 you have to learn 3 languages to do that.
Re:COBOL programmers answer call by dmix on Saturday April 11, 2020 @01:34AM (#22839810)
HTML and CSS are more markup languages than actual languages. You can work at varying degrees of abstraction.

There are thousands of template sites being used today with JS plugins the developer probably wouldn’t know how to write. But the minimal interface layers are sufficient to get them to work.

Stuff like Select2 and bootstraps collection of plugins cover a broad range of interactivity most people need on the internet.

Re:COBOL programmers answer call by zitterbewegung on Friday April 10, 2020 @08:03PM (#22838631)
What you are describing sounds like the inverse of TRAMP in modern GNU emacs.
Re:COBOL programmers answer call by gumby on Friday April 10, 2020 @08:44PM (#22838806)
In a way. We had that too, with a networked filesystem in the 1970s so you could simply open a remote file in ITS EMACS (or any other program). It was handled by the O/S, or rather a user space program like today’s FUSE.
Re:COBOL programmers answer call by larsbrinkhoff on Tuesday April 14, 2020 @05:38AM (#22864123)
But the bulk of the remote file system code was in user space.
Re:COBOL programmers answer call by rbanffy on Friday April 10, 2020 @08:07PM (#22838644)
Or an HTML form.
Re:COBOL programmers answer call by gumby on Friday April 10, 2020 @08:41PM (#22838795)
SUPDUP was far more dynamic than an HTML form (read RFCs 734 and 749).

html forms are more like the half duplex terminals of the 70s/80s.

Re:COBOL programmers answer call by m463 on Saturday April 11, 2020 @01:45AM (#22839848)
I remember someone complaining about unix machine in comparison to mainframes:

"It generates an interrupt every time you press a key!"

Re:COBOL programmers answer call by DonHopkins on Saturday April 11, 2020 @05:09AM (#22840580)
At UMD, Chris Torek hacked ^T support to the 4.2 BSD tty driver, inspired by TOPS-10/TWENEX's interrupt character that displayed the system load, current running job, etc.

But the first version didn't have any de-bouncing, and would process each and every ^T it got immediately (each of which had a lot of overhead), so on a hardwired terminal you could hold the keys down and it would autorepeat really fast, bringing the entire system to its knees, while you could even watch the load go up and up and up!

And of course whenever the system got slow, everybody would naturally start typing ^T at once to see what was going on, making it even worse.

That was a Heisenbug, where the act of measuring affects what's being measured, with an exacerbating positive feedback loop. He fixed the problem by rate-limiting it to once a second.

https://en.wikipedia.org/wiki/Heisenbug

https://en.wikipedia.org/wiki/Positive_feedback

Re:COBOL programmers answer call by goatinaboat on Saturday April 11, 2020 @02:46AM (#22840049)
VMS systems on LAT networks only received a packet/interrupt per line from the terminal, that’s how they were able to support many times more users than Unix contemporaries.
Re:COBOL programmers answer call by gumby on Saturday April 11, 2020 @03:23AM (#22840187)
Unix can be configured this way —- it used to be the default, with # as the rubout character and @ the line delete character. It’s still in the tty driver and can be useful when programming from a teletype (tty)
Re:COBOL programmers answer call by goatinaboat on Saturday April 11, 2020 @03:49AM (#22840277)
I learnt something today - thanks. I’ve never seen a Unix system configured like that, in over 25 years of doing this!
Re:COBOL programmers answer call by gumby on Saturday April 11, 2020 @12:35PM (#22842515)
That system was inherited from Multics, but the limited number of interactive computers in those days were primarily used from printing terminals which couldn’t actually erase a character so all of them had some such facility.
Re:COBOL programmers answer call by m463 on Saturday April 11, 2020 @08:50AM (#22841402)
thank goodness. I remember it was common that the login screen on a terminal would be configured for # as backspace while backspace would actually DO a backspace but be entered into the buffer.

I suspect it was a remnant of hardcopy terminals

Re:COBOL programmers answer call by msla on Saturday April 11, 2020 @12:42AM (#22839679)
> Terminals like the 3270 were even half duplex so would process the input and then send it off as a block, to make the channel controllers more efficient!

The block mode terminals (like the 3270) were/are kinda like HTML forms: The mainframe sends a form to the terminal, and the terminal has enough local smarts to know how forms work, that only some regions of the form are writable, and how to send a response back one form at a time, as opposed to the character-at-a-time terminals which Unix and VMS and ITS were built around. There's a lack of flexibility, but it allows mainframes to service tons of interactive users, for a certain definition of interactive.

The Blit terminal was the next step beyond block mode terminals, in some sense: Blits could be character-cell terminals with fundamentally the same model as the VT100, but they could also accept software in binary form and run interactive graphical programs locally. Think WASM, only with machine code instead of architecture-independent bytecode.

https://en.wikipedia.org/wiki/Blit_(computer_terminal)

> When initially switched on, the Blit looked like an ordinary textual "dumb" terminal, although taller than usual. However, after logging into a Unix host (connected to the terminal through a serial port), the host could (via special escape sequences) load software to be executed by the processor of the terminal. This software could make use of the terminal's full graphics capabilities and attached peripherals such as a computer mouse. Normally, users would load the window systems mpx (or its successor mux), which replaced the terminal's user interface by a mouse-driven windowing interface, with multiple terminal windows all multiplexed over the single available serial-line connection to the host.

> Each window initially ran a simple terminal emulator, which could be replaced by a downloaded interactive graphical application, for example a more advanced terminal emulator, an editor, or a clock application. The resulting properties were similar to those of a modern Unix windowing system; however, to avoid having user interaction slowed by the serial connection, the interactive interface and the host application ran on separate systems—an early implementation of distributed computing.

That was 8th and 9th Edition Research Unix; it was an influence on Plan 9, which took the distributed GUI computer system concept and ran with it.

> So you could log into a remote machine and run EMACS, and while you were editing a remote file with a remote editor all the screen updating would be done by your local computer!

Also, ITS had the neat feature of detaching job trees: You could login, get your own HACTRN (the hacked-up debugger ITS used as a shell), run a few other programs which would then be children of that HACTRN job, and detach the whole tree and logout. When you logged back in, you could re-attach the tree and carry on like nothing happened. It's kinda like screen or tmux.

Re:COBOL programmers answer call by DonHopkins on Saturday April 11, 2020 @05:24AM (#22840639)
>Also, ITS had the neat feature of detaching job trees: You could login, get your own HACTRN (the hacked-up debugger ITS used as a shell), run a few other programs which would then be children of that HACTRN job, and detach the whole tree and logout. When you logged back in, you could re-attach the tree and carry on like nothing happened. It's kinda like screen or tmux.

You could also detach any particular job sub-tree, and other users could reattach it. Useful for passing a live ZORK or LISP or EMACS back and forth between different logged-in users. "Here, can you fix this please?"

There was also a :SNARF command for picking a sub-job out of a detached tree (good for snarfing just your EMACS from your old HACTRN/DDT tree left after you disconnected, and attaching it to your current DDT).

https://github.com/PDP-10/its/blob/master/src/sysen1/ddt.154...

It helped that ITS had no security whatsoever! But it had some very obscure commands, like $$^R (literally: two escapes followed by a control-R).

There was an obscure symbol that went with it called "DPSTOK" ("DePoSiT OK", presumably) that, if you set it to -1, allowed you to type $$^R to mess with other people's jobs, dynamically patch their code, etc. (The DDT top level shell had a built-in assembler/debugger, and anyone could read anybody else's job's memory, but you needed to use $$^R to enable writing).

Since ITS epitomized "security through obscurity", the magic symbol DPSTOK was never supposed to be spoken of or written down, except in the source code. But if you found and read the source code, then you passed the test, and deserved to know!

There was a trick if you wanted to set DPSTOK in your login script (which everyone could read), or if somebody was OS output spying on you (which people did all the time), and you wanted to change their prompt or patch some PDP-10 instructions into their job without them learning how to do it back to you.

The trick was to take advantage of the fact that DPSTOK happened to come right after BYERUN. So you could set BYERUN/-1, which everybody does (to run "BYE" to show a joke or funny quote when you log out), then type a line feed to go to the next address without mentioning it name, then set that to -1 anonymously.

So knowing the name and incantation of the secret symbol implied you'd actually read the DDT source code, which meant you had high moral principles, and were qualified to hate unix, which didn't let you do cool stuff like that. ;)

https://github.com/larsbrinkhoff/its-archives/blob/master/em...

    From: "Stephen E. Robbins" <[email protected]>
    Date: Thu, 21 Dec 89 13:25:56 EST
    To: CENT%[email protected]
    Subject: Where unix-haters-request is

       Date: Wed, 20 Dec 89 22:13:42 EST
       From: "Pandora B. Berman" <CENT%[email protected]>

       ....Candidates for entry into this august body must either prove their
       worth by a short rant on their pet piece of unix brain death, or produce
       witnesses of known authority to attest to their adherence to our high
       moral principles..

    Does knowing about :DDTSYM DPSTOK/-1 followed by $$^R qualify as attesting
    to adherence of high moral principles?

    - Stephen
Here are the symbols in the source:

https://github.com/PDP-10/its/blob/master/src/sysen1/ddt.154...

    BYERUN: 0 ;-1 => RUN :BYE AT LOGOUT TIME.

    DPSTOK: 0 ;-1 => $$^R OK on non-SYS jobs
Here's the $$^R handling code that slyly prints out " OP? " to pretend it didn't understand you. (In case anybody's watching!)

https://github.com/PDP-10/its/blob/master/src/sysen1/ddt.154...

    N2ACR: SKIPN SYSSW ;$$^R
          jrst n2acr0 ;  Not the system?
        SETOM SYSDPS
        jrst n2acr9

    n2acr0: skipn dpstok ;Feature enabled?
          jrst n2acr9 ;  nope
        skipe intbit(U) ;Is it foreign?
          jrst n2acr9 ;  no, either SYS (special) or our own (OK anyway!)
        movei d,%URDPS
        iorm d,urandm(u)  ;turn on winnage
    n2acr9: 7NRTYP [ASCIZ/ OP? /]
Re:COBOL programmers answer call by acdha on Friday April 10, 2020 @08:12PM (#22838665)
This had some neat benefits: in the 90s I worked for a COBOL vendor (Acucorp) who had a bytecoded portable runtime which allowed you to run a binary on systems ranging from 16-bit DOS to Windows NT, most Unix variants, VMS, etc. (our QA matrix had ~600 platforms & versions). The display section meant it could adjust to the platform: on DOS and other consoles, you had text controls but on X11, Win16/32, OS/2, and Mac it had native GUI widgets, with native validation UI. It wasn’t beautiful out of the box but it was familiar, consistent, and accessible.

The same was true of the standard indexed storage: a different runtime could use a SQL database for storage without recompiling the program, which was key to some gradual migrations to Java. A similar feature allowed remapping invoke calls to run on a remote server.

At one point we produced a NPAPI plugin version: install it in Netscape and your client ran the UI while the data access and RPC calls happened on a server. All I can say is that it seemed like a good idea at the time.

Re:COBOL programmers answer call by downerending on Friday April 10, 2020 @06:42PM (#22838100)
I've not used this, but it reminds me some of the UI of early Lotus 1-2-3 (in text, no GUI). It was amazingly intuitive and easy to navigate, even without a mouse.

Modern web apps, each unique and confusing, with no reliable way to move focus around and with bizarre text entry "improvements", would have made the Admiral weep.

Re:COBOL programmers answer call by zozbot234 on Friday April 10, 2020 @07:43PM (#22838519)
> Modern web apps, each unique and confusing, with no reliable way to move focus around

If accessibility is set up correctly, you can still move focus with TAB and activate widgets/buttons with SPACE or ENTER. No different from any terminal app. If client-side JS is being used, the web page could even display additional forms in response to a keyboard shortcut, with no network-introduced latency.

Re:COBOL programmers answer call by betenoire on Friday April 10, 2020 @08:00PM (#22838616)
Accessibility is only part of it. You should know where your keys are going to take you, and tabs often become unpredictable and confusing
Re:COBOL programmers answer call by badsectoracula on Saturday April 11, 2020 @06:39AM (#22840954)
> move focus with TAB and activate widgets/buttons with SPACE or ENTER. No different from any terminal app

No different from a terminal app that pretends to be a GUI app :-P. At the minimum many terminal/DOS apps used arrow keys to move between fields and often just pressing enter in a field (often after it was validated), it'd move to the next relevant field. Shortcut keys to move around and/or perform context sensitive functions (e.g. search for product IDs in a field where you are supposed to enter a product ID) would also be available at any time.

I remember my father making a program for his job (for his own use) ~20 years ago in Delphi and he was manually wiring all the events to move around with the Enter key, like his previous program (written in DOS and Turbo Pascal) did and was annoyed that he had to do this manually.

TBH i do not believe it is impossible to do this nowadays on the web, but just like it wasn't done in the majority of GUI desktop apps that followed the DOS days, i also do not believe it is/will be done in the web apps that is done nowadays. The reasons for this vary, but i think a large part of it is that people simply haven't experienced using the other methods to even think about them.

Re:COBOL programmers answer call by int_19h on Monday April 13, 2020 @01:28PM (#22857886)
It wasn't done by the apps, because the standard UX on all those platforms did not include move-focus-on-Enter - and GUI apps are generally supposed to follow the standard.

FWIW I agree that for data entry apps in particular, Enter is just too convenient - and I had to write code to manually implement it in GUI apps, as well.

Re:COBOL programmers answer call by downerending on Saturday April 11, 2020 @01:20AM (#22839779)
Per sibling, even at best, this just isn't in the same league. And I'm doubtful about "best".

And even if it works, why should I need to enable special accessibility features to access a UI mode that isn't utter sh_t?

Re:COBOL programmers answer call by eitland on Saturday April 11, 2020 @03:11AM (#22840141)
> Modern web apps, each unique and confusing, with no reliable way to move focus around and with bizarre text entry "improvements"

I'd not vote to go back to the 90ies (we've fixed way to many security problems since then) but it would be great if we could all agree that we lost something along the way and try to get it back somehow while keeping the things that work today.

Re:COBOL programmers answer call by wgyn on Friday April 10, 2020 @07:05PM (#22838266)
That is a great video! It also reminds me of Dan Wang's essay on How Technology Grows: https://danwang.co/how-technology-grows/. It introduced me to the Ise Grand Shrine, which is a wooden temple that's rebuilt and torn down periodically so that the knowledge of how to maintain it doesn't get lost.
Re:COBOL programmers answer call by dylan604 on Friday April 10, 2020 @08:19PM (#22838702)
>Regarding the underlying theme of legacy systems, here is an interesting presentation by Jonathan Blow, citing various examples of earlier civilizations losing access to technologies they once had

This is why printed physical books are still an important thing in the age of eReaders and the like. Also, the Library of Congress archives audio on vinyl. The ancient analog formats will still be able to be understood in 100 years. Today's latest tech won't be though. I was just provided a CD-R/DVD-R(didn't look that close) of x-rays of my cat. I honestly have no way of reading that data as none of my devices have a x-ROM drive.

Re:COBOL programmers answer call by badsectoracula on Saturday April 11, 2020 @04:16AM (#22840379)
Eh, not really a problem. Your CD-R issue is pretty much the same as you not having a cylinder phonograph player - a device that is already 100 years old. Sure, if you do not have such a player you cannot play the cylinder, but the audio stored in those players isn't lost, players exist for those who want to listen to the cylinders and given enough money, new ones can be made.

Similarly, you may not have a CD-R or DVD-R reader, but it takes about 5 euros to buy one and access your CD. In 100 years it might cost more, but i'm willing to bet that CD-R and DVD-R readers will still be available in much greater numbers than cylinder phonograph players are. Making new ones, for really important data, will certainly be more expensive than making a new cylinder player but it wont be impossible - if the data is important enough and for some reason all the millions of CD-R players in existence nowadays has vanished, a new one will be made.

And analog formats aren't that great either - most of them tend to wear over time, so they have their own drawbacks.

Re:COBOL programmers answer call by tbyehl on Saturday April 11, 2020 @01:17PM (#22842775)
Mr Wizard taught me how to improvise a record player [1]. I doubt our great-grandchildren will be able to improvise a CD reader.

[1] https://www.youtube.com/watch?v=HJa6Ik6xmiU

Re:COBOL programmers answer call by karatestomp on Saturday April 11, 2020 @08:41AM (#22841356)
External DVD writer (so, also CDs) drives are about $30 now for a decent brand, powered entirely over their USB cable so no power brick to mess with, and are about half an inch thick and barely bigger than the discs that go in them. One can easily live in a junk drawer, unnoticed until needed. I was surprised to discover how tiny and low-power they are now, and how cheap.
Re:COBOL programmers answer call by dylan604 on Saturday April 11, 2020 @10:38AM (#22841889)
That's great for today. In 10 years? 20 years? Definitely worthless in 100. Even the $30 today is wasted money for me. I have friends that have antiquated tech laying around in a junk drawer that I could easily borrow if I needed. Instead, I just requested the vet attach the data on the disc in an email. Even cheaper and less tech waste involved.
Re:COBOL programmers answer call by xigency on Friday April 10, 2020 @10:10PM (#22839170)
That’s funny. I have a Blu-ray Drive only so I can make physical backups of some important things to store.
Re:COBOL programmers answer call by tantalor on Friday April 10, 2020 @06:40PM (#22838084)
> quickly create user interfaces by declaratively describing them

> everything can be accessed using only the keyboard

Sounds like plain old html forms.

Re:COBOL programmers answer call by triska on Friday April 10, 2020 @06:43PM (#22838111)
Yes, at least in some respects, HTML forms could have been that way, but in practice, they are not:

For one thing, and this is important, with every browser I tried, I get periodically interrupted by messages that the browser displays and that are not part of the form. Just recently, I was again asked for security updates by the browser. Sometimes when opening a form it gets prefilled by the browser, sometimes not, and sometimes only some of the fields. Some other times I get asked whether the browser should translate the form. Sometimes it asks me whether some fields should be prefilled. Sometimes when submitting a form the browser asks me whether I would like to store the form contents for later use. Sometimes the browser asks me at unpredictable times whether I would now like to restart it.

An important prerequisite for getting a lot of work done is for the system to behave completely consistently and predictably, and not to interfere with unrelated messages, questions, alarms etc. This is also very important for training new users, writing teaching material etc.

Another important point, and that is very critical as well, is latency: Just recently, I typed text into my browser, and it stalled. Only after a few moments, the text I entered appeared.

I never had such issues with COBOL applications. Today, we can barely even imagine applications that are usable in this sense, because we have gradually accepted deterioration in user interfaces that would have been completely unacceptable, even unthinkable, just a few decades ago.

Re:COBOL programmers answer call by K0SM0S on Friday April 10, 2020 @09:17PM (#22838985)
Of all the woes of modern UI, latency on text input is what I find most irritating. It's physical, visceral, mental, I don't know; when you've been raised by incredibly snappy video games (1980-1990s, 2D glory), it's asinine to suffer input lag in 2020 of some x86 platform. It's just alien an experience, like time suddenly reversed for userland or something.

In the browser, given the steaming pile of code that some pages have become, I may understand some lag, quirks. They broke the web and Chrome is helping so... Yeah. But in a text editor of all applications? No. I mean, just... no. (Looking at you, atom, vscode... WHY?)

Whatever the hell you're trying to search / display / message (I assume, trying to help me...): please begin by not interrupt my input feedback? That should be, I don't know, the only sane priority for UX, to actually respond to the user? Otherwise the computer feels... broken, subpar, unfit for the task? Am I alone in having these feelings when using devices?..

/rant over. I'm not that old for god's sake, 37 and they've got me jaded by UX quality already. All it took was two short decades to flush down the drain the precious good that didn't need fixing.

Ah. I'm sure we'll get back there. Eventually. Even if I have to write it myself (surely, we'll be legions). Someday I wonder what we're waiting for. And then I remember that this is the year of the Linux desktop... It's not that easy, is it?

Re:COBOL programmers answer call by torgian on Friday April 10, 2020 @11:05PM (#22839372)
I gotta agree here. UX seemed so simple just ten- twenty years ago... and still I wonder how the hell people programmed 16 bit video games in a tiny system.

And everything on the web front is so bloated. Yes, I can make a pretty UX with that, but at what cost? I think that the faster and cheaper computers that we have today have made it easier to overlook how bloated everything has become.

Upside is, it does make a lot of things easier. Downside is, everything is slower and fatter. Mostly because of new frameworks, languages, etc that all aim to accomplish something, just easier.

And I get it. I understand why we want to make it easier. But again, what are the costs?

Re:COBOL programmers answer call by zozbot234 on Friday April 10, 2020 @11:13PM (#22839396)
> And everything on the web front is so bloated.

Um, you're posting this on a site that's basically the polar opposite to "bloat" on the web. Badly-engineered systems have always existed somewhere; even the COBOL-based proprietary solutions referenced in the OP are a fairly obvious example of that.

Re:COBOL programmers answer call by torgian on Friday April 10, 2020 @11:56PM (#22839545)
Ok, then the _majority_ seems to be bloated. And I feel like this is the new normal.

HN, in my opinion, is an island of simplicity in a sea of complexity.

Re:COBOL programmers answer call by K0SM0S on Saturday April 11, 2020 @11:59AM (#22842315)
This is pure speculation on my part but I like to think that there's literally billions to save. It's about the order of magnitude: even 1 minute per year per person amounts to something like 15,000 man-days (>100 million man hours!).

1 minute per year!

Re:COBOL programmers answer call by badsectoracula on Saturday April 11, 2020 @04:22AM (#22840406)
I have a feeling that many programmers and engineers are blind to latency. Not in a sense that they are bad programmers/engineers, but in a sense that they simply cannot feel the difference, so they make stuff that introduce latency they themselves cannot perceive.

So you get stuff like Wayland that introduces latency issues and when you try to explain the issue you feel like trying to describe the difference between magenta and fuchsia to a blind person.

Re:COBOL programmers answer call by K0SM0S on Saturday April 11, 2020 @11:49AM (#22842255)
Oh my, I've never thought of it this way. I really get what you mean.

Can't agree more. That might very well be it.

Could it be trained, through exposure, e.g. with video games as I implied?

Or is it maybe related to "snapiness" of the brain?— I think it's been shown that we clearly have difference response times, some people being several times faster/slower than others (with no explicit correlation to a "level" of intelligence", more like the characteristics of different engines in terms of latency / acceleration / max speed / torque / etc).

Re:COBOL programmers answer call by badsectoracula on Saturday April 11, 2020 @06:11PM (#22844621)
TBH i don't know. I was playing video and computer games since a very young age, so it might have to do with this but at the same time i know i wasn't paying much attention to latency until my late 20s. Even at 25 i'd be running Beryl (one of the first compositors) with its massive latency and i'd be writing games with software rendered mouse cursors, both being incredibly poor in terms of latency and i'd just not notice it.

So perhaps it can be learned?

Re:COBOL programmers answer call by kierank on Friday April 10, 2020 @09:44PM (#22839077)
Re:COBOL programmers answer call by flyinghamster on Friday April 10, 2020 @07:42PM (#22838506)
The other thing about too many modern user interfaces is that they often get subjected to whatever fad is in vogue this week. Eye candy takes precedence over consistent user interfaces, and gratuitous changes are routine because a new fad has become the Next Big Thing.
Re:COBOL programmers answer call by tomlagier on Friday April 10, 2020 @07:34PM (#22838467)
The trade-off, of course, is access. Now, computers are cheap and available everywhere. In the COBOL era, what percentage of a family's income would it take to purchase such a machine? How wide-spread were these machines in non-English speaking areas? How easily could a program from one of the machines be used on a machine built by a different vendor? Were said programs resilient to malicious actors?

As always, there are sacrifices, but in general I think we have made rational trade-offs in this realm.

Re:COBOL programmers answer call by chrisweekly on Friday April 10, 2020 @07:57PM (#22838603)
Not to mention executing the program across different kinds of wired and wireless networks, and handling a huge variety of client OS, user agent, and input modalities.
Re:COBOL programmers answer call by hrktb on Friday April 10, 2020 @11:16PM (#22839412)
You seem to be complaining more about the browser than HTML per se. Why not use another browser ? or even a lynx like browser then ?

I think despite all of these most of us stick with modern browsers because the tradeoffs are worth it. Removing complexity and unpredictability at all costs has usually worse impacts than being annoyed and surprised. Except if your software drives a cockpit or a nuclear plant.

Re:COBOL programmers answer call by zozbot234 on Friday April 10, 2020 @07:52PM (#22838568)
> For one thing, and this is important, with every browser I tried, I get periodically interrupted by messages that the browser displays and that are not part of the form. ...

Pressing the ESC key should dismiss these messages. It's an annoyance to be sure, but not a deal breaker. Similar for pre-filled content, you can just select and erase it.

Re:COBOL programmers answer call by K0SM0S on Friday April 10, 2020 @09:30PM (#22839029)
Sadly, <ESC>it doesn'<ESC>t really solve t<ESC>he problem of interrupting one's fl<ESC>ow...

At least, such behavior should be user preference— “get out of my way” is like #1 on most users list for a useful toggle.

As for notifications specifically, it's not like we haven't developed 101 notification centers to postpone user response.

The problem, imho, with qualifying this as universally "not a deal breaker" is that it's a slippery slope, all too subjective to boot with— e.g. is Windows auto-rebooting not a deal breaker either? I'm sure to some people, not really...

A showstopper has very different thresholds depending on what you do. Live tasks notably (recording, streaming, etc) should be sanctuarized (down to a "real-time" setting at the thread level, when it's not actually unstable for some ungodly reason). Chrome is just another OS nowadays, videoconference being a prime example of app. I wouldn't like Chrome to nag me during an interview for instance.

If I even have to make just 1 extra move, gesture, click, whatever even a look away from my work, because the machine demands that I do (screen or app locked 'behind' otherwise), in effect creating unsollicited gates between me and my workflow... yeah, there's a big problem. 5 minutes saved a day per user for a big corp is millions saved before a month has passed.

Now think that we're collectively, computer users, like one big human corporation. Think of the time we're losing due to bad design. Let that sink in for a minute... It's a huge and stupid cost we impose on ourselves. Must be funny to some, idk...

There is a way to a better UX. We shouldn't need ESC to get there. ;-)

Re:COBOL programmers answer call by wrs on Friday April 10, 2020 @07:04PM (#22838258)
Indeed, and in fact there are systems that adapt between the two paradigms. For example, taking a system based on IBM 3270 screens and turning it into a series of web pages to enable a web portal for an existing mainframe system.
Re:COBOL programmers answer call by sjburt on Friday April 10, 2020 @07:44PM (#22838520)
I worked for a company that had one of these ancient (probably mainframe) systems for inventory, business analytics etc. Users at the factory would access it via 3270 terminal emulators. It was clunky but usable.

Until they wanted to stop paying for terminal emulator licenses and replaced it with a web gateway that translated the 3270 pages into HTML forms. That was pretty horrible to use and of course people began “forgetting” to record inventory moves and process steps. This was for six figure aerospace components so at the end of the day someone knew where they all were and what had been done, it just made it a lot harder to bill for milestones and wasted tons of time. Of course the software was like $15 a seat.

Re:COBOL programmers answer call by acdha on Friday April 10, 2020 @08:13PM (#22838672)
Plain HTML5 forms: they had complex field structures and validation which required JavaScript until we got things like the extra input types and regex patterns.
Re:COBOL programmers answer call by Pmop on Friday April 10, 2020 @08:14PM (#22838678)
Kinda but not entirely off-topic. Low-tech magazine is all about solar power these days but previous issues brought back to light technologies we once used, and probably would be still useful these days; plus, you get to save power, lower carbon footprint, and so on.

https://www.lowtechmagazine.com/

Re:COBOL programmers answer call by scythe on Friday April 10, 2020 @06:44PM (#22838124)
>For instance, it allows programmers to quickly create user interfaces by declaratively describing them, in a so called SCREEN SECTION.

>The resulting interfaces are very efficient for text entry, and allow users to quickly get a lot of work done. The interaction is so much more efficient than what we are used to with current technologies that it can barely be described or thought about in today's terms.

It's not common anymore, but Unix clones still have dialog(1):

https://www.freebsd.org/cgi/man.cgi?query=dialog

Re:COBOL programmers answer call by apfsx on Friday April 10, 2020 @06:30PM (#22837987)
Do you have a video that shows an example of this text entry system? I'm interested in seeing this.
Re:COBOL programmers answer call by triska on Friday April 10, 2020 @06:35PM (#22838041)
Sometimes I see it on terminals for instance when checking into a hotel, opening an account in a bank, booking a flight, interacting with the tax administration etc.

One important point that makes them so efficient to use is that everything can be accessed using only the keyboard.

For my personal use, I have simulated such forms using Emacs, and especially its Widget Library:

https://www.gnu.org/software/emacs/manual/html_mono/widget.h...

This is a bit similar to what you get with a SCREEN SECTION in COBOL.

Re:COBOL programmers answer call by userbinator on Friday April 10, 2020 @06:47PM (#22838143)
Anyone who has used the BIOS setup function of a PC before the EFI bloat took over will find that interface familiar, it's certainly easy to use and quite efficient.

Here's an example screenshot: http://www.buildeasypc.com/wp-content/uploads/2011/11/step12...

Re:COBOL programmers answer call by epc on Friday April 10, 2020 @06:50PM (#22838166)
Re:COBOL programmers answer call by Zenst on Friday April 10, 2020 @06:49PM (#22838161)
In the early 80's we had terminals (Newberry being one brand iirc)that would talk to the mainframe and in this instance a Honeywell Bull DPS8 range and these terminals had block mode, so could just type out using the cursor keys to navigate and key in all your code or feild attributes as you would for a transactional screen layout input interface. Then having effectly edited and dealt with localy, could hit send into the edit buffer and covered much WYSWYG form of input and layout for screens. So many ways of doing screen editing and text entry in the real early pre PC days would of been down to the terminals and local cursor, send whole screen block mode form of editing. Unlike character mode (very early systems way of pooling terminals) in which it had to handshake each and every keystroke in effect. Though even some of these terminals could be configured to allow full screen editing mode and sent via character mode batch polling. Terminals were not cheap back then either and when the PC came out, terminal emulation software was one of the big sellers in some markets who would spend lots on the early PC's and more on this software as cheaper than the dedicated terminal offerings.
Re:COBOL programmers answer call by adzm on Friday April 10, 2020 @06:29PM (#22837981)
I was blown away by some reporting systems in COBOL that were surprisingly understandable and simple.
Re:COBOL programmers answer call by wglb on Friday April 10, 2020 @06:38PM (#22838065)
The only way I found COBOL palatable was to spend the better part of a year programming in RPG III first.
Re:COBOL programmers answer call by icedchai on Friday April 10, 2020 @11:11PM (#22839393)
If only it were so easy to do that with modern web technologies. Instead, you write dozens (if not hundreds) of lines of HTML/CSS/JS just to do a simple form post. And it feels like it's gotten worse over the years.
Re:COBOL programmers answer call by dzonga on Friday April 10, 2020 @07:16PM (#22838358)
thanks for the Jonathan blow talk. very informative and good to reflect on. e.g in software younger dev's don't generally accept the advice of the older gen. hence we keep reinventing tech instead of iterating. examples been serveless vs php deployment. k8's, react etc
Re:COBOL programmers answer call by thereyougo on Saturday April 11, 2020 @02:08AM (#22839930)
Wow, I was sure that COBOL is not being used any more since the new programming languages are just better in any aspect.

What's the reason that COBOL faded over the years?

Re:COBOL programmers answer call by goatinaboat on Saturday April 11, 2020 @02:52AM (#22840080)
the new programming languages are just better in any aspect.

Well, you should question your assumption that the new languages are better. They aren’t, they are just more fashionable. You can see this in every aspect of life, not just programming. Previous generations liked high-quality products that would last. Modern day people like cheap objects that soon break and are thrown away and replaced with something equally cheap and flimsy.

There’s a reason that COBOL (and FORTRAN) code is still running 50 years later, and that last year’s JavaScript already needs to be rewritten.

Re:COBOL programmers answer call by onei on Saturday April 11, 2020 @03:23AM (#22840184)
It depends how you quantify better. If you mean easier to hire developers in, provides higher levels of abstraction, etc. then modern programming languages are generally better. If you value stability and cost, as those who own these COBOL do, then you don't care about what it's running on and what you have is good enough until it suddenly isn't. 50 years is a long time to find bugs and modern applications don't have anything close to that level of hardening.
Re:COBOL programmers answer call by goatinaboat on Saturday April 11, 2020 @03:42AM (#22840249)
you mean easier to hire developers in, provides higher levels of abstraction, etc. then modern programming languages are generally better

That’s a subtle distinction, in JavaScript a high level of abstraction means hiding the details of the DOM and how the interface works, whereas in COBOL or FORTRAN what you’re really abstracting is the problem domain itself.

Availability of programmers is part driven by the market but largely by programmers themselves who try to avoid mature and established technologies and chase the hottest new trend. So it’s true what you say, but it doesn’t happen because it has to but because people want it to.

Re:COBOL programmers answer call by hacker_9 on Friday April 10, 2020 @09:26PM (#22839017)
Have you used imgui? Easily fastest way to create a GUI since dawn of computing, Cobol screen section really has nothing on it.
Re:COBOL programmers answer call by analognoise on Friday April 10, 2020 @09:47PM (#22839088)
Compared to Tkinter (or even straight Tk)?

If you want something naive that I think blows both out of the water: FreePascal/Lazarus.

Re:COBOL programmers answer call by okareaman on Saturday April 11, 2020 @01:27AM (#22839797)
Everything Old is New Again
Re:COBOL programmers answer call by m463 on Saturday April 11, 2020 @02:38AM (#22840029)
little known fact - COBOL is very efficent - in terms of errors.

I recall it won an award for the most error messages from the fewest number of lines of code.

I think a program with a period in column 6 run through the IBM Cobol compiler would generate either 200 or 600 lines of error messages.