Why not just write javascript? Though that's my argument against any of these compile to js kits (coffee script being the big one). So maybe I'm just trolling (sorry).
Again, super cool. The author is waaay smarter than I for implementing this, but... The real world.
Quick comment from the author: #1 has already been addressed by emitting Source Maps. With a supporting browser, you can debug your Scala.js application easily. You get positions in the original source code, breakpoints in the original source code, stack traces in the original source code, etc.
It will be long before someone implement this in the real world (website). It needs 16MBs download for the standard libs. Even twitter only downloads around ~2MBs before showing page.
Comments
While in principal, I love this... Because JS is not my favorite language... I just don't see the real world benefit. It's going to:
1.) increase difficulty debugging (compiled js -> scala) 2.) decrease productivity, see #1
Why not just write javascript? Though that's my argument against any of these compile to js kits (coffee script being the big one). So maybe I'm just trolling (sorry).
Again, super cool. The author is waaay smarter than I for implementing this, but... The real world.
I can only speak for clojurescript, but I'm ok with trading off some debugging pain for way better semantics / nicer code.
Hi,
Quick comment from the author: #1 has already been addressed by emitting Source Maps. With a supporting browser, you can debug your Scala.js application easily. You get positions in the original source code, breakpoints in the original source code, stack traces in the original source code, etc.
It will be long before someone implement this in the real world (website). It needs 16MBs download for the standard libs. Even twitter only downloads around ~2MBs before showing page.