Comment on Scrape: A simple, higher level interface for Go web scrapingComments−rdudekul11yTo me goquery seems more intuitive than scrape, may be because I am more familiar with jquery selectors syntax.Any reason why yhat guys (ericchiang) created Scrape (and not use say goquery)?Can you make the matcher function in main.go go away with a simpler (more intuitive) interface/api/dsl?−ericchiangOP11yThis is a very small amount of boilerplate around the golang.com/x/net/html package. If you need the huge feature set of goquery, use that. But I find this pretty suitable for my day to day problems.−zippoxer11yI agree. Reading the title, I thought scrape would offer something beyond HTML manipulation.The way that it is now, goquery provides easier and more familiar HTML manipulation.
Comments
To me goquery seems more intuitive than scrape, may be because I am more familiar with jquery selectors syntax.
Any reason why yhat guys (ericchiang) created Scrape (and not use say goquery)?
Can you make the matcher function in main.go go away with a simpler (more intuitive) interface/api/dsl?
This is a very small amount of boilerplate around the golang.com/x/net/html package. If you need the huge feature set of goquery, use that. But I find this pretty suitable for my day to day problems.
I agree. Reading the title, I thought scrape would offer something beyond HTML manipulation.
The way that it is now, goquery provides easier and more familiar HTML manipulation.