Scrapism
scrapism.lav.io
Scrapism
1–10 of 30 posts
Re: Scrapism
#2- Getting all comic's image and converting to e-book for my Kindle.
- Surveying info for buying new house.
- Helping my wife in collecting data for her new writing.
- Transferring all my Facebook fanpage post to my personal blog
And I did enjoyed my journey in scraping thing to make my life easier and full of joy.
Re: Scrapism
#3Re: Scrapism
#4This is free(!) to host, and the commit log gives an enormous amount of detail about how the scraped resource changed over time.
I wrote more about this trick here: https://simonwillison.net/2020/Oct/9/git-scraping/
Here are 267 repos that are using it: https://github.com/topics/git-scraping?o=desc&s=updated
Re: Scrapism
#5I usually create some small scraping script for my daily life. - Getting all comic's image and converting to e-book for my Kindle. - Surveying info for buying new house. - Helping my wife in collecting data for her new writing. - Transferring all my Facebook fanpage post to my personal blog And I did enjoyed my journey in scraping thing to make my life easier and full of joy.
Re: Scrapism
#6A trick I think would be useful to include here is running scrapers in GitHub Actions that write their results back to the repository. This is free(!) to host, and the commit log gives an enormous amount of detail about how the scraped resource changed over time. I wrote more about this trick here: https://simonwillison.net/2020/Oct/9/git-scraping/ Here are 267 repos that are using it: https://github.com/topics/git-s…
Re: Scrapism
#7Is Python still the most common tool used for web scraping and if so, what's the advantage over jsdom/cheerio or, say a headless browser based tool like puppeteer?
I've been using these tools for years, but I grew up in the JS world, so I'd be curious to hear people with different backgrounds/biases than mine:)
Re: Scrapism
#8Tangentially related question: Is Python still the most common tool used for web scraping and if so, what's the advantage over jsdom/cheerio or, say a headless browser based tool like puppeteer? I've been using these tools for years, but I grew up in the JS world, so I'd be curious to hear people with different backgrounds/biases than mine:)
Re: Scrapism
#9Back in 2015, the author reported using CasperJS to scrape public LinkedIn profiles. The author reported this was a PITA.
Here the author recommends using WebDriver implementations, e.g., chromedriver or geckodriver, in addition to scripting language frameworks such as Puppeteer and Selenium. Is scraping LinkedIn still a PITA.
Because the examples given are always relatively simple, i.e., not LinkedIn, I am skeptical when I see "web scraping" tutorials using Python frameworks and cURL as the only recommended option for automated public data/information retrieval from the www.[FN1,2] I use none of the above. For small tasks like the examples given in these tutorials, the approaches I use are not nearly as sophisticated/complicated and yet they are faster and use fewer resources than using Python and/or cURL. They are also easier to update if something changes. That is in part because (1) the binaries I use are smaller, (2) I do not rely on scripting languages[FN3] and third party libraries (and so much less code involved), (3) the programs I use start working immediately whereas Python takes seconds to start up and (4) compared to the programs I use, cURL as a means of sending HTTP requests is inflexible, e.g., one is limited to what "options" cURL provides and cURL has no option for HTTP/1.1 pipelining.
1. LinkedIn's so-called "technological measures" to prevent retrieval of public information have failed. Similarly, its attempts to prevent retrieval of public information through intimidation, e.g., cease-and-desist letters and threats of CFAA claims, have failed. Tutorials on "web scraping" that extol Python frameworks should use LinkedIn as an example instead of trivial examples for which using Python is, IMHO, overkill.
2. What would be more interesting is a Rosetta Code for "web scraping" tasks. There are many, many ways to do public data/information retrieval from the www. Using scripting languages such as Python, Ruby, NodeJS, etc. and frameworks are one way. That approach may be ideally suited for large scale jobs, like those undertaken by what the author calls "internet companies". But for smaller tasks undertaken by individual www users for noncommercial purposes, e.g., this author's concept of "scrapism", there are also faster, less complicated and more efficient options.
3. Other than the Almquist shell
Re: Scrapism
#10Tangentially related question: Is Python still the most common tool used for web scraping and if so, what's the advantage over jsdom/cheerio or, say a headless browser based tool like puppeteer? I've been using these tools for years, but I grew up in the JS world, so I'd be curious to hear people with different backgrounds/biases than mine:)
I'm a bit of a Python zealot, but if you prefer JS then use JS. The best tool is the one you know.
I think Python became the scraping language because many people thought it was significantly easier to use than Perl, and Perl was on top because it was significantly easier than shell scripting. Any language that is incrementally easier, or better in other aspects wont inspire people to learn something new. If we had node 15 years ago, maybe it would have been JS.
As far as headless browsers, selenium has official Python bindings. Though I kind of consider that cheating.
For my personal taste, I choose Python because I can write it off the top of my head without making syntax errors, or leaning on an IDE. It's the only language I can do that with, and I've been able to do it since about a month into using it.