Re^4: Embedding WebPerl Code Demos into Other Pages

it's a very long time since I used Java applets, so I'm not sure about that side...

I see some similarities but also advantages.

you only need to have JS activated in the browser, no external add-ons/plug-ins necessary
once the Perl interpreter is downloaded and in the cache you won't have much start-up lack when loading new code.*
you can easily reuse JS libs and naturally interact with the DOM, no alien Java panel/interface.

due to JIT compiling will JS still be much faster, but you'll be able to reuse CPAN modules inside the browser.

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice}

*) though I'm not sure if a "warm start-up" is possible without using frames.

Comment on Re^4: Embedding WebPerl Code Demos into Other Pages

Replies are listed 'Best First'.
Re^5: Embedding WebPerl Code Demos into Other Pages by haukex (Archbishop) on Oct 13, 2018 at 08:16 UTC
I agree with your points on Java applets vs. JavaScript! though I'm not sure if a "warm start-up" is possible without using frames AFAICT most of the start-up time comes from fetching the two relatively large files `emperl.data` (~2.5MB compressed) and `emperl.wasm` (~1.1MB compressed), so as long as those are cached, it should be ok, no matter if frames are used or not. Of course, caching has to be implemented correctly and enabled both on the client and on the server, e.g. a `If-Modified-Since` + `304 Not Modified` exchange. (On Chrome Mobile loading is also fairly slow compared to Firefox Mobile, but I'm not yet sure why.)	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^5: Embedding WebPerl Code Demos into Other Pages
by haukex (Archbishop) on Oct 13, 2018 at 08:16 UTC

I agree with your points on Java applets vs. JavaScript!

though I'm not sure if a "warm start-up" is possible without using frames

AFAICT most of the start-up time comes from fetching the two relatively large files emperl.data (~2.5MB compressed) and emperl.wasm (~1.1MB compressed), so as long as those are cached, it should be ok, no matter if frames are used or not. Of course, caching has to be implemented correctly and enabled both on the client and on the server, e.g. a If-Modified-Since + 304 Not Modified exchange. (On Chrome Mobile loading is also fairly slow compared to Firefox Mobile, but I'm not yet sure why.)

[reply]
[d/l]
[select]