4 ms·
There's a "Features and comparison" section on the linked page that addresses exactly this.
by pipeep 11y ago
There's a "Features and comparison" section on the linked page that addresses exactly this.
- solomatov 11y agoThey didn't persuade me in anything. Even worse, I don't understand some of them. What're well typed Java libraries. BTW, GWT, support in browser java debug via sourcemaps for a long time.
- chii 11y agoSource maps doesn't compare to actual debugging that GWT used to be able to do (via a browser plugin). GWT died the day they decided that they will no longer support that.
- cromwellian 11y agoIt wasn't the GWT team that made this decision, it was the browser vendors. They killed the NPAPI. For good reason too, it was a major source of insecurity. PPAPI (NaCL) could not replace what was lost, because modeling JVM -> JSVM -> JVM calls requires synchronous re-entrant execution. BTW, you don't have to debug in Chrome. If you attach IntelliJ to the JSVM, you can debug right inside your IDE, stepping over breakpoints in Java, etc. SDBG for Eclipse does the same things. (https://www.youtube.com/watch?v=icJEa5lcJaQ https://www.youtube.com/watch?v=icJEa5lcJaQ)
- chii 11y agoAs far as I can tell, you cannot eval arbitrary expressions. I used to use it like a REPL back then. That's what I would miss now with source map
- cromwellian 11y agoIt might be possible to pull this off with the new compiler because it's draft mode is a true incremental unoptimized draft, and translating an expression to call the JS is a relatively straightforward ABI.
- solomatov 11y agoActually, source maps and browser based debugging are quite good. They aren't as good as Java debugger, but good enough. I am working on a large scale project which uses GWT, and we are absolutely ok with source map debugging.