My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
motifanalytics.medium.com
My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
1–10 of 37 posts
Re: My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
#2I’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).
Re: My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
#3How persistent can you make this data?
Re: My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
#4I’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).
In the past few years there was this blog post[0] that clarified this. It moved the restriction on serving a "disproportionate percentage of pictures, audio files, or other large files" to another part of the TOS dedicated specifically to the CDN part[1] and clarified that, if you're using Cloudflare add-on services Stream, R2 (their S3), or Cloudflare Images, then you won't be at risk of termination.
0: https://blog.cloudflare.com/updated-tos/
1: The restriction still exists at https://www.cloudflare.com/service-specific-terms-applicatio... under "Content Delivery Network (Free, Pro, or Business)".
Re: My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
#5Tip 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
#6Tip 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.
This guide can help if you still want the code to be pretty: https://www.taniarascia.com/adding-syntax-highlighting-to-co...
Re: My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
#7Tip 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.
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.
Re: My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
#8[dead]
Re: My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
#9Tip 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.
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:
Re: My Browser WASM't Prepared for This. Using DuckDB, Apache Arrow and Web Workers
#10Earlier 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/
I’m disappointed the rendered picture isn’t advanced CSS. I honestly expected that to be the case.