3 ms·
(2) is also much less resource intensive as well. Who knows how much JS on may end up executing on Twitter's homepage.
by nemothekid 13y ago
(2) is also much less resource intensive as well. Who knows how much JS on may end up executing on Twitter's homepage.
- wslh 13y agoBenchmark your personal time developing a Twitter web scraper similar to this one to the time to follow the (2) approach. The code of the article was done in a few hours while the (2) approach would require further analysis and risks (analyzing protocols can be very tricky). Google Chrome and Firefox are very fast and one developer day may cost more than one PC.
- nemothekid 13y agoWell at the end of the day, the application really matters. In most cases I find just sniffing the XHR requests with Chrome's Developer Tools to be the most productive.