4 ms·
Hi there, co-author here. Always to improve the content we're writing here. What else would you have expected to read in such an article?
by daolf 4y ago
Hi there, co-author here.
Always to improve the content we're writing here. What else would you have expected to read in such an article?
- danmur 4y agoI think it's a pretty good article personally, sounds like the complaint is just about the title :P
- edent 4y agoI think it is good. You have to remember that some of the loudest voices on here take things extremely literally. They have no concept of hyperbole for emphasis. Or, indeed, anything which makes writing interesting to read. Is your guide everything someone needs to know? No. But anyone literate in the ways of modern English understands what you mean. It is an excellent guide and I think you should consider expanding it & perhaps creating a book. Please don't be discouraged by the people on here who don't have the skill or courage to write or submit anything.
- CJefferson 4y agoNowadays I would jump straight to selenium (or similar), as most websites feature AJAX or similar, so need a full browser. Then, you don't actually do anything with selenium, click a button / link, or anything interesting.
- daolf 4y agoAgreed, this is why on the Selenium paragraph we link to this article that go much more in depth https://www.scrapingbee.com/blog/selenium-python/ https://www.scrapingbee.com/blog/selenium-python/
- pfranz 4y agoWhile it's true I often end up needing something like selenium, it's way more heavy handed and I usually reach for it last. It doesn't scale as well, harder to troubleshoot IMHO, and more libraries and dependencies to deal with in a language where that's already not great.