J's environment has its roots in the earliest days of computing -- when operating system command lines were not a thing.
To some degree, this is great -- we have the J command line, and we have varied environments like jqt and jhs. On the other hand, this has meant J's support for the various OS command lines ... still has some room for improvement. Specifically, when I start a J program in jconsole, there are various things I might want to do: (1) I might want to use code which depends on jqt and/or jhs. (2) I might want to figure out which directory my script and/or the j interpreter resides in. These things are easy when I am running code that I wrote myself. It's tougher when I hand it off to someone else to use. It's kind of easy if I can assume that they're a programmer, who can be counted on to install J, and is interested in doing so. Not so much if they're expecting something else. Anti-malware measures, in particular, turn this whole scene into a nightmare. Anything which is too easy eventually gets slapped down because someone somewhere took advantage of it. And then there's the ongoing deprecations -- where old stuff no longer works with newer J interpreters. --------------- I am not proposing any specific resolutions here. I am just outlining a situation. I have had some solutions in mind, but other people have tended to have conflicting approaches. FYI, -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
