I’ve been toying with the idea of implementing a distributed analytics engine on top of Cloudflare workers and DuckDB. I’m not sure if this goes against the CloudFlare TOS tough (last time I checked they had some provisons against processing images).
My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
11–20 of 37 posts
Re: My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
#12Earlier quoted context omitted.
Pro tip for everybody: do not post any text as images Never should I receive a Java exception hundreds of lines long as a cut off JPEG file. Or a screenshot of a Google Sheet missing the information you’re talking to me about.
We made this to be used as a reply when pictures are misused where text would be better: https://fewer.pics/
Re: My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
#13Re: My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
#14Earlier quoted context omitted.
We made this to be used as a reply when pictures are misused where text would be better: https://fewer.pics/
Why ruin the message by writing half of it upside down?
Hopefully this sparks a little “wow I wonder if my image of text was also hard to read like I just experienced” moment.
Re: My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
#15Tip for all the blog authors, do NOT post code as image. Specially do not add fake editor UI and drop shadow to the image. In this case 25 lines of code is 50 kB of image binary. Also it cannot be searched via search engine. Nor can it be read with screen reader.
Re: My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
#16Re: My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
#17Re: My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
#18Tip for all the blog authors, do NOT post code as image. Specially do not add fake editor UI and drop shadow to the image. In this case 25 lines of code is 50 kB of image binary. Also it cannot be searched via search engine. Nor can it be read with screen reader.
Re: My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
#19Tip for all the blog authors, do NOT post code as image. Specially do not add fake editor UI and drop shadow to the image. In this case 25 lines of code is 50 kB of image binary. Also it cannot be searched via search engine. Nor can it be read with screen reader.
Re: My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
#20We use the WASM build of DuckDB quite extensively at Count ( https://count.co - 2-3m queries per month). There are a couple of bugs we've noticed, but given that it's pretty much maintained by a single person seems impressively reliable!