> Having used APL professionally for ten years from the early 80's to early 90's

That might be part of problem. Things have happened since then:

Dyalog has made the full product available for free, only asking for 2% of any profit you make once you cross a certain threshold. Open-sourcing the interpreter is under consideration.

Dyalog has a built-in compiler.

Dyalog's new function form, dfns, has variables local by default.

Dyalog has fully integrated C#-style OO system.

Dyalog has ⎕NA for seamlessly calling C functions as if they were APL functions.

Names Associated (⎕NA) C functions can be called inline

Dyalog namespaces are objects that are not class-based, but with named members

Dyalog's tradfns allow name-lists for multiple required arguments (and results)

True, there are no multi-line comments in any APL yet, but Dyalog allows writing {condition : result if true ⋄ result if false}

Dyalog has :Select which is similar to switch but allows case-lists.

I'm not sure what you mean by "APL-run-time-definable comparison operator", but any function can be used in place of the built-in ones. (This wasn't always the case, but certainly is now.

It is quite easy to check for the data type of given input, e.g. using the Data Representation function (⎕DR).

Putting the statement in a named function allows you to compile it separately from the surrounding code.

Right, no real-time extensions integrated into the language.

The co-dfns library allows you to offload computations to the GPU.

Dyalog's 1111⌶ allows you to select how many cores to use.

Right, no built-in interface for custom hardware-based acceleration

Dyalog's binary arrays use true bit-binary representation.

Dyalog's at operator @ and the index function ⌷ combined with the rank operator ⍤ provide full control over and flexibility in multidimensional array indexing.

Dyalog has supported SCM monitored text files for many years, and the built-in tools are only getting better and better.

Not sure what you have in mind with regards "Genetic and Evolutionary computing primitives built into the language."

The stencil operator ⌺ is a Neural Network/Cellular Automaton primitive built into the language.

Dyalog has some native support for image manipulation, has various libraries too, and deep integration with .NET.

Much of NumPy is of course APL breakfast, and there are math libraries for certain other things. In the worst case, use PynAPL to call Python.

Dyalog has the spawn operator & for multi-threaded/multitasked computing.

I'm not sure network access and processing would be suitable as primitives with glyphs, but Dyalog's Conga library provides this, and may well get further integrated into the interpreter in the future.

Dyalog's multi-core and distributed computing primitives are currently accessed with cover functions, but the ¤ and ∥ symbols have been reserved already.

Built-in primitives for data exchange? ⎕JSON, SQAPL, and ⎕XML etc.

Dyalog's ⎕R and ⎕S provide Perl-compatible regular expressions.

I'm not so sure all quad names should have symbols. Many of them have related or prefixed names, e.g. ⎕Nxyz for file functions and ⎕Txyz for thread-handling. That said, plenty of new Unicode symbols have been added lately.