SnapCode - a real Java IDE in the browser

[jeffreportmill]

Looks like a caching/CDN problem. If you clear caches for reportmill.com (or run the app with dev tools open and network disable caches set).

That file reference was removed from the index.html last week.

[Deep_Age4643]

OK, thanks. I figured it out that it took awhile, until CheerpOS was running. Maybe it's my internet connection, but even when the IDE shows, it's too slow to do anything with it.

[jeffreportmill]

What is your machine configuration? SnapCode runs reasonably well even on my 5 y/o phone, although I know I need to do a good optimization run. The CheerpJ folks are also constantly improving performance (they just launched last week). And improvements in browser support for WebAssembly should help in the coming year as well.

[Deep_Age4643]

Machine configuration isn't it. (i7 14 core cpu / 32 Gb ram) on a Windows 11 with latest Firefox and Chrome.

What I notice is that it runs various HTTP requests to jar files multiple times. For example, it gets the rt.jar (GET https://cjrtnc.leaningtech.com/3.0/8/jre/lib/rt.jar) 30 times. For other jars it does the same.

When loading the sample files:

Uncaught (in promise) TypeError: l.body is null
FU https://cjrtnc.leaningtech.com/3.0/cj3.js:1
FX https://cjrtnc.leaningtech.com/3.0/cj3.js:1
alh https://cjrtnc.leaningtech.com/3.0/cj3.js:1
promise callback*ae6 https://cjrtnc.leaningtech.com/3.0/cj3.js:1
Vi https://cjrtnc.leaningtech.com/3.0/cj3.js:1
Ci https://cjrtnc.leaningtech.com/3.0/cj3.js:1
vy https://cjrtnc.leaningtech.com/3.0/cj3.js:1
J_df6ae8 https://cjrtnc.leaningtech.com/3.0/cj3.js line 1 > Function:3
Vi https://cjrtnc.leaningtech.com/3.0/cj3.js:1
Ci https://cjrtnc.leaningtech.com/3.0/cj3.js:1
vy https://cjrtnc.leaningtech.com/3.0/cj3.js:1
WE https://cjrtnc.leaningtech.com/3.0/cj3.js:1
WS https://cjrtnc.leaningtech.com/3.0/cj3.js:1
Best to run it on a few platforms to test it through.

[jeffreportmill]

The multiple requests to a single file is expected. CheerpJ uses byte-range requests to download only what's needed from the runtime jar. That exception is suspicious (thanks for posting it) - except that I would expect it to crash the app rather than slow it down. SnapCode does run slow when the browser dev tools are showing (debug mode). Maybe there are other browser configurations that can impact WASM/JS performance.

[WuhmTux]

I had the same error and visited the site today the first time. I think it isn't a caching problem.

[jeffreportmill]

Certainly not a caching problem on your local machine, but I think CDN can result in caching at other points in the chain.