Re^2: WebPerl in a Progressive Web App?

> For the latter, a PWA alone doesn't automatically mean Perl keeps running in the background - one would have to fire up an interpreter in a Web Worker, independently of whether it's a PWA or not.

my concerns were that a cold start of webperl implies

megabytes of web-perl environment need to be fetched from the net
time to start the compiler and compile the code.
getting the interpreter ready

I was thinking of having a hot Perl server in at least a FastCgi'ish way in the WebWorker and communicating with the webpage. ( Prepared till the INIT phase)

I was hoping that this hot start is considerably faster.
That response is competing speed wise with pure JS code.
And that bigger memory overhead° can be handled by swapping dormant PWAs to disc.

Please correct me if my assumptions were to naive...

> but it's still those same megabytes that have to be passed around,

I'm ignorant about the amount of megabytes needed in RAM.

On a tangent: Did you try running Mojolicious inside WebPerl?

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

see Wikisyntax for the Monastery}

°) tho I forgot how much RAM is needed then

Comment on Re^2: WebPerl in a Progressive Web App?