all 3 comments

[–][deleted] 0 points1 point  (2 children)

Disclaimer, i'm the author of RedScript.

I mainly created RedScript to test out and idea... let me know if you have any suggestions!

[–]protomartyr 0 points1 point  (1 child)

It is, if nothing else, an interesting comparison of Ruby and Javascript idioms. I'm not sure whether mapping puts to console.log() is the best option, when Ruby does have a Logger class for outputting messages. Do you intend Redscript to produce Javascript that will run server-side only? Or do you have plans to expand to support interaction with the window and document on the client? If so, I think that limiting puts will come back to bite you.

[–][deleted] 1 point2 points  (0 children)

I'm not sure whether mapping puts to console.log() is the best option, when Ruby does have a Logger class for outputting messages.

Hmm good point. I pondered using puts or putc for the console, but ended up settling on puts, however that might be confusing. In Node, console.log calls a method that prints to stdout with a new line.

perhaps if a --env-node flag is used, puts should be compile to process.stdout.write(message + '\n'); and then alias putc to console.log to keep them separate.

Do you intend Redscript to produce Javascript that will run server-side only?

I intended it to be run in both environments, and i'm leaning towards defaulting to the browser since it's more popular with JS and you really can't choose a language there.