Skip to content
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

typo: same uses cases --> same use cases #454

Closed
classbasics opened this issue Nov 15, 2020 · 3 comments
Closed

typo: same uses cases --> same use cases #454

classbasics opened this issue Nov 15, 2020 · 3 comments

Comments

@classbasics
Copy link

Please replace every line in curly brackets { like this } with appropriate answers, and remove this line.

Description

typo: same uses cases --> same use cases

Location of Content

https://dev.grakn.ai/docs/comparisons/semantic-web-and-grakn

Expected Content

same use cases

Actual Content

same uses cases

Additional information

{ Any additional information, including logs or screenshots if you have any. }

@classbasics
Copy link
Author

I have just finished reading through the docs.
Despite the problems I think Grakn may be useful.
I have concerns about its efficiency with no benchmarking data.
Maybe a combination of Grakn and Scylladb with Node.js as middleware would be better.
There are few Node.js code examples, so there is another hurdle.
AWS Grakn is an old version running on ebs, where I was thinking of nvme.
I was hoping version 2.0 would come out in October 2020, with promised performance enhancements.
Maybe I will look back at Grakn in January 2021.
Good luck with fixing the docs.

@flyingsilverfin
Copy link
Member

flyingsilverfin commented Jul 14, 2021

Hi there --
thanks a bunch for the the incredibly thorough feedback on our docs! They were probably a fair reflection of how many developers viewed the getting started journey... hopefully now it is slightly better.

I did not address the high-level story of the docs (your related issues: #458, #407, #411) as this is meant to be addressed in a rewrite soon, but we do know this is an issue! The other changes I made I did to improve the state for short term, because that rewrite has been pushed back a few times already.

We hope you have had time to revisit TypeDB 2.0 - it really is much faster and more stable, building on RocksDB directly.

@jamesreprise
Copy link
Contributor

No longer exists.

@jamesreprise jamesreprise closed this as not planned Won't fix, can't repro, duplicate, stale Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants