Yomguithereal

I would not call this ASCII art per se. Some of the used characters are not ASCII. How about Unicode art?

> ‘Safely’. An attacker who has control over a row in that file can easily embed data that satisfies the statistical checks, thus injecting data.

This is clearly not the sort of thing you should expose to anyone, it is an optimization technique. The same way you would not use a fast but DOSable hash function for your hashmap.

TL;DR: Seeker struct from simd-csv Rust crate knows how to perform approximate random access in a CSV file [1]

The `xan` command line tool is therefore able to use it to perform single-pass map-reduce parallelization over CSV files and also binary search within sorted CSV data! [2]

[1]: https://docs.rs/simd-csv/latest/simd_csv/struct.Seeker.html [2]: https://github.com/medialab/xan/

There is a section here with a table describing the kind of boost you might observe vs. rust-csv used by xsv: https://docs.rs/simd-csv/latest/simd_csv/#regarding-performa...

the reversing bytes part is encoding agnostic. you just feed the reversed bytes to the csv parser then re-reverse both the yielded rows and the cells bytes and get the original order of the bytes themselves.

xan is a maintained fork of xsv

xan is a maintained fork of xsv

A good way to parallelize CSV processing is to split datasets into multiple files, kinda like manual sharding. xan has a parallel command able to perform a wide variety of map-reduce tasks on splitted files.

https://github.com/medialab/xan

I would add xan to this list: https://github.com/medialab/xan

But of course, I am partial ;)

An equivalent for Titanium: https://github.com/yuchi/react-titanium

no more

I think you are right. It's time we give a proper name to these unidirectional data flow architectures and fly away from the Flux naming.

Hello DougBTX. Could you post an issue on the repository describing what you would need for this library to work nicely with TypeScript so we can see whether things can be improved?

This is an interesting point. I created an issue on the github repository concerning this matter. Maybe you'd like to comment on it about your use case so we can improve the tool?

This would indeed be nice and this is precisely what we intend to code next.

Backend and frontend scraping just don't attend the same needs. Running backend monsters to scrape small to medium amount of data only once is such a drag when frontend scraping can take less than half an hour to perform the same task. Plus you can see the results of your code live while browsing the DOM comfortably. Finally, nobody prevents you from using artoo backend when you execute javascript.

jquery is injected carefully by artoo so it does not break anything on the host page. However, CSP override is not default on artoo and you have to install the chrome extension to perform this. But this extension has solely to be activated when scraping and only developers should use them while knowing its effects.