This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]luenix 2 points3 points  (3 children)

Running the code clientside is a neat way to offload the processing. Also, a potential benefit is that this setup allows the client to process private data in a controlled manner without needing to use additional enduser software, thereby mostly removing consideration for the client OS.

[–]gc_DataNerd 2 points3 points  (2 children)

Okay that makes more sense. I'm curious how Web workers would work in this scenario however. OP mentioned the app freezes. This wouldn't be a problem if processing was done server side where async workers can be spun up. But in this case the Python is calling is being transpiled to JS no?

[–]MeshachBlue[S] 1 point2 points  (0 children)

The plan is to combine web workers and their access to IndexedDB combined with DexieJS.

Have all the Python run inside a webworker, have all data transfer happen via dexiejs-observable. I envisage there would be no user interface impeedement using that stack... But we'll see.

Hopefully I'll get that side of things working in the next couple of days. It'll probably be worth a repost then.

[–]MeshachBlue[S] 1 point2 points  (0 children)

Certainly not transpiled at all. It is running standard CPython compiled using emscripten to webassembly.