Overall Unofficial Roadmap

[joshgoebel]

I was speaking with Ruby and this list was entirely off the cuff but I thought I'd include it here and we can update it over time and turn it into more of an actual plan:

• get the input stuff sorted out so it's not painful to use the repl ((end) support Emoji and UTF-8 input in CLI #71 and (chore) refactory CLI history #72 needs testing)
• make sure Stdin/Stdout etc is good (wren-cli should fflush(0) before returning with a successful exit code #56, io.Stdout.flush() ignores output errors rather than ensuring output buffers get written #59, wren-cli should support reading from stdin #55, Stdin tests fail on windows/mac  #27, Stdin.readLine aborts when reading from a file #29, Stdin.readByte is broken. #17)
• File / Directory / IO rounded out (Improve file/directory utils #84)
• child process stuff done properly (including std redirections etc) (I've started on this with (enh) adds Process.exec(cmd, [args], [cwd],[env]) #94 but no redirection support)
• basic networking (tcp)
• higher level networking (http etc)

[clsource]

Is there really a need for basic networking? My opinion is that component can be externalized via extensions.
In my opinon a higher priority than networking would be extensability via plugins or dynamic libs 👍

[joshgoebel]

This was before the discussion happening in #93. So perhaps it should be understood as a list of "what should CLI be capable of doing" rather than "what all is built in"... though I think all the other stuff is good (and most of it's there already save process handling).

This is still a good rough draft 0.1 list whether networking is in or out of scope though. :-) Can't do much without networking these days. :)

[PureFox48]

Can’t do much without networking these days. :)

Very true and personally I think there should be some networking support in the CLI’s standard modules even if it’s fairly basic.