rdflib.js VS crawlee

Another possibly useful resource is https://docs.inrupt.com/developer-tools/javascript/client-libraries/, detailing the various JS tools Inrupt provides. Was thinking this could be useful to share, along with https://github.com/linkeddata/rdflib.js/, which is a powerful tool for working with Linked Data in JavaScript.

There's also rdflib.js (https://github.com/linkeddata/rdflib.js/) if you want another approach to handling linked data.

> Talking about RDF is absolutely meaningless without talking about Serialisation (and that includes ...URGH.. XML serialisation), XML Schema data-types, localisations, skolemisation, and the ongoing blank-node war.

Don't implement XML serialization. The simplest and most widely used serialization is n-quads (https://www.w3.org/TR/n-quads/). 10 pages, again with exaples, toc, and lots of non-normative content.

You don't need to handle every data type, and you can't even if you wanted to because data types are also not a fixed set. And whatever you need to know about skolemisation, localization, and blank-nodes is in the standards AFAIK.

> C'mon, rdflib is a joke. It has a ridiculous 200 issues / 1 commit a month ratio, buggy as hell, and is for all intents and purposes abandonware.

It works, not all functionality works perfectly but like I said I have used it and it worked just fine.

> rdflib.js is in memory only, so nothing you could use in production for anything beyond simple stuff. Also there's essentially ZERO documentation.

For processing RDF in browser it works pretty well, not sure what you expect but to me RDF support does not imply it should be a fully fledged tripple-store with disk backing. Also not really zero documentation: https://github.com/linkeddata/rdflib.js/#documentation

> > What are the alternatives?

> SIMPLICITY!

> But the great thing about it is that there could be dozens of equally simple systems and standards, and we could actually see which approaches are best, from usage.

Okay, so you roll your own that fits your use case. Not much use to me and it is not a standard. Lets talk again when you standardize it. Otherwise do you mind giving an alternative that I can actually take off the shelf to at least the extent that I can with RDF?

I am not going to roll my own standard, and if all the RDF data sets instead used their own standards instead of RDF it won't really improve anything.

In this guide, we'll be extracting information from Amazon product pages using the power of TypeScript in combination with the Cheerio and Crawlee libraries. We'll explore how to retrieve and extract detailed product data such as titles, prices, image URLs, and more from Amazon's vast marketplace. We'll also discuss handling potential blocking issues that may arise during the scraping process.

Previously, the Apify SDK offered a blend of crawling functionalities and Actor building features. However, a recent update separated these functionalities into two distinct libraries: Crawlee and Apify SDK v3. Crawlee now houses the web scraping and crawling tools, while Apify SDK v3 focuses solely on features specific to building Actors for the Apify platform. This distinction allows for a clear separation of concerns and enhances the development experience for various use cases.

v3.1 added an error tracker for analyzing and summarizing failed requests.

Closest I found was https://crawlee.dev/ for Javascript/Typescript although still seems not on the level of scrapy. I didn't try it.

Also, you can go even further and develop your own web scraper with Crawlee, a Node.js library that helps you pass those challenges automatically using Puppeteer or Playwright. Crawlee helps you build reliable scrapers fast. Quickly scrape data, store it, and avoid getting blocked with headless browsers, smart proxy rotation, and auto-generated human-like headers and fingerprints.

https://crawlee.dev/ its very good, you can easily run your spiders in cloud with apify, and nodejs/puppeteer has many advantages than python/selenium

Apify is a platform for web scraping that helps the developer starting from the coding, having developed its open-source NodeJs library for web scraping called Crawlee. Then on their platform, you can run and monitor the scrapers and also finally sell your scrapers in their store.

You can use our open source tools (not only this one, but also Crawlee for example) to build your scrapers and run them on your computer, and then if you need to run them in the cloud, you can upload them to the Apify platform and run them there. Our free tier is good enough for smaller web scraping and automation projects, and if you need more compute resources or proxies, you can go for one of our paid tiers.

Comfortable scraping and crawling with Puppeteer is better done together with another library. This library is called Crawlee, and it's also free and open-source, just like Puppeteer. Crawlee wraps Puppeteer and grants access to all of Puppeteer's functionality, but also provides useful crawling and scraping tools like error handling, queue management, storages, proxies or fingerprints out of the box.