Code playground sucks if you need user input... Or is it just me

Question

What's the deal with having to put in all inputs at the beginning of the run?
it ruins the ability to use loops effectively unless you user read the code and can antiscipate all the answers to the prompts before they are given.

Answer 1

"If the program need to wait for user input then it's going to hold the server's memory resource indefinitely which is no good."

Related
https://www.sololearn.com/Discuss/728769/?ref=app

Answer 2

If you think about it, the platform does not offer you any kind of terminal. All it does is compile the program, run it on its servers and then return what it has on it's screen (mildly put).
It just doesn't support runtime user inputs because of the architecture of it.

Answer 3

suuuuuuucks

Answer 4

I am using an Android phone to follow the password generator challenge that is trending. one of the perameters of the challenge is that the program asks the user for the length of the pasword to be generated....so...I have done this....as well as having a question at the end that will stop or continue the process of password generating. anyway....when I am in the code playground and press the "run" button, I get a pop up prompt that says
"looks like your program needs input"
"split multiple input into separate lines"

my keyboard comes up and I am supposed to ender inputs for all the possible times that I may be asked for one if I want the program to run properly.

Answer 5

Indeed, it's not perfect sadly.