-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Improve the Features section in README #772
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added two comments which I think improve the spelling or wording.
The rest is my subjective commentary on the matter of Crawlee and Scrapy comparison, which you can take as a feedback, but also completely ignore. I wanted to provide an outsider perspective, but at the same time, I think the framework creators should have the freedom to express their opinionated view and their ambition how the project should differentiate.
Just chiming in, not approving nor disapproving.
Co-authored-by: Honza Javorek <[email protected]>
@honzajavorek, thanks for your feedback. |
One more thing I didn't notice previously - I'm sorry! Most of the points start with "Crawlee something..." or "unlike Scrapy, Crawlee..." Given the heading already sets the scene, I think we can be shorter by just listing the benefits:
Something along these lines. Feel free to drop my suggestion or get just loosely inspired by it. |
Co-authored-by: Honza Javorek <[email protected]>
No description provided.