These are chat archives for opal/opal

21st
Jul 2016
Zak Storer
@zacts
Jul 21 2016 01:40
hello
Mitch VanDuyn
@catmando
Jul 21 2016 01:45
Hello
Mitch VanDuyn
@catmando
Jul 21 2016 18:09
I just opened #1539 - would appreciate any help to getting a work around...
I thought I could do this:
#application.rb
require 'opal'
STDOUT.write_proc = `console.log`

but I can't seem to get it to "stick" - In otherwords by the time opal is actually executing STDOUT has still got its original definition...
I feel like the short term solution would be to issue a separate require file as part of the opal package so you could do:

require 'opal'
require 'opal/console-output'

which would force STDOUT to use the console...

@fkchang - I would really to understand @searls reasoning...
Mitch VanDuyn
@catmando
Jul 21 2016 18:15
If I didn't have opal, I would certainly think JS everywhere was less mad than having to constantly switch languages, and/or divide my development skills artificially along some boundry determined strictly by 1990's internet capabilities...
So my order from bad to good would be: multiple domain specific languages -> JS everywhere -> Ruby Everywhere -> vacation anywhere!