Re:Show HN: Chunkify.js – A functional API to unblock your J...
by nacs on Sunday October 04, 2015 @04:39PM
(#10328728)
You should have the "chunkify" checkbox on by default (or at least warning before people hit one of the Map/Reduce buttons).
People are likely getting their browser tab (perhaps their whole browser) frozen when they click those buttons and having to bail out on your page/submission.
Also, add some overview text instead of a blank page with a ball on it like:
Re:Show HN: Chunkify.js – A functional API to unblock your J...
by yangmillstheory on Sunday October 04, 2015 @04:59PM
(#10328801)
It works - and that's the core of what's being done if you look at the code. I just wanted to make something re-usable, configurable, and play around with ES6 generators :).
Re:Show HN: Chunkify.js – A functional API to unblock your J...
by Retr0spectrum on Monday October 05, 2015 @12:09PM
(#10332739)
Do you think it would be possible to dynamically adjust the chunk size for optimum performance on different hardware/browsers? That would be very useful.
Re:Show HN: Chunkify.js – A functional API to unblock your J...
by yangmillstheory on Monday October 05, 2015 @12:28PM
(#10332913)
The API exposes the chunk/delay parameters as options, so it's definitely possible.
If you mean having the library code "learn" the optimal chunk/delay for a given run, that's possible too, but I'd have to wonder about alternative solutions at that point.
Re:Show HN: Chunkify.js – A functional API to unblock your J...
by Retr0spectrum on Monday October 05, 2015 @12:10PM
(#10332747)
One problem I found with web workers is that they do not respond to messages when inside a tight loop, which can be problematic in certain circumstances. I actually used a similar technique inside a web worker for that reason.
Re:Show HN: Chunkify.js – A functional API to unblock your J...
by DiThi on Sunday October 04, 2015 @10:09PM
(#10329619)
I got over that limitation by converting the code to a data URL, like this:
var blob = new Blob([worker_code_string], {type: 'application/javascript'});
var worker_uri = (window.URL || window.webkitURL).createObjectURL(blob);
var worker = new Worker(worker_uri);
The path to the scripts imported with importScript() must be absolute, though. I add the path by modifying worker_code_string. Alternatively they can be fetched and prepended to the code string (or passed in the array of Blob()).
Re:Show HN: Chunkify.js – A functional API to unblock your J...
by Kequc on Monday October 05, 2015 @12:21PM
(#10332862)
I was reading about that. It seems pretty strange that these heavy security restrictions on origin are in place but you can create a worker from a string.
Re:Show HN: Chunkify.js – A functional API to unblock your J...
by hippich on Monday October 05, 2015 @11:39AM
(#10332517)
in my project HashcashIO[1] i get around that using iframe and loading main script for same domain. while restrictions exist, i believe it is easier to get around them (basically write code in secure fashion) rather than trying to break work into junks in the main thread.
Although, depending on task i see cases where chunkify.js will be useful, since i myself used this idea, granted with adhoc implementation instead of using well defined library.
People are likely getting their browser tab (perhaps their whole browser) frozen when they click those buttons and having to bail out on your page/submission.
Also, add some overview text instead of a blank page with a ball on it like:
https://github.com/yangmillstheory/chunkify
I'll add an explanation of what's happening.
If you mean having the library code "learn" the optimal chunk/delay for a given run, that's possible too, but I'd have to wonder about alternative solutions at that point.
Although, depending on task i see cases where chunkify.js will be useful, since i myself used this idea, granted with adhoc implementation instead of using well defined library.
[1] https://hashcash.io/