I'm glad we're talking about this because there may be misconceptions of how things work or perhaps I am not seeing the issue.
Your example, when run, will only affect the specific browser tab that code is run in. If that browser tab is reloaded, it starts with a fresh temporary, in-memory file system. If a new browser tab is opened, it gets its own temporary in-memory file system. In other words, it does no harm except to that specific session. The J Playground does not touch the host operating system. It runs sandboxed in the browser. The risk to me is that someone could write some code that taxes the CPU (maybe mines cryptocurrency ;) ), but presumably a script like that will be more easy to spot because the playground doesn't run code automatically. Or, someone may write some code that blows up the memory of the tab, which causes the browser to kill the tab. Browsers have gotten quite good at keeping poor performing websites or operations from crushing the system. On Thu, Jun 2, 2022 at 5:56 PM Paul Jackson <[email protected]> wrote: > At the moment there is an open door to anyone who knows, or cares to learn > about J. > 'Testing' fwrite 'tmp/this.txt' > At a minimum, we could make the directories write protected from the > account running the interpreter. > > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
