Top all-time · #6524
open.dgraph.io
Company blog · open.dgraph.io/postdataprogramming
open.dgraph.io is the company blog at open.dgraph.io, writing about data and programming. Since 2016, 12 different Hacker News readers have linked it 21 times, most often “Show HN: Golang implementation of custom encoding in net/rpc vs. grpc.io”. No feed was found, so read it on the site itself.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
HN readers link this blog for its post explaining Dgraph's licensing, including its move from Apache 2 to AGPLv3 and how the server code is licensed. Commenters use it to explain the change and debate copyleft licensing.
Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- /post/licensing/3 people · 3 mentions · first linked 2017-04-09
- Show HN: Golang implementation of custom encoding in net/rpc vs. grpc.io2 people · 2 mentions · first linked 2016-06-27
What Hacker News says?
Three separate points here: 1) copyleft versus non-copyleft 2) which copyleft license to choose 3) the strategy of the dgraph Regarding 1), non-copyleft leads to higher short-term adoption, but copyleft is often the better choice long-term. Moreover, history has shown that if you switch from a non-copyleft to a copyleft license, people will feel tricked. So the "early stage" argument doesn't hold. If you want to use…
Comment linking /post/licensing/
on “Badger – A fast key-value store written natively in Go”Submitted Badger – A fast key-value store written natively in Go as a story · 355 points
HN discussionhttps://open.dgraph.io/post/licensing/
Comment linking /post/licensing/
on “Badger – A fast key-value store written natively in Go”Submitted Dgraph v0.7.1: Highly Available Using RAFT as a story · 21 points
HN discussionoff topic: flipping through the dgraph code, I noticed their licensing switch from Apache 2 to AGPLv3, anyone involved around to comment? Adding a draconic open source license is an unwise decision for an early stage database product imo ( https://open.dgraph.io/licensing is a dead link)
Comment linking /licensing
on “Badger – A fast key-value store written natively in Go”Submitted Show HN: Gru – Open source solution for better technical interviews as a story · 13 points
HN discussionDgraph follows MongoDB licensing. The clients are all in Apache, and the server code is AGPL. This doesn't affect anyone using Dgraph for commercial purposes; but if they make changes to the server code, they'll have to release them under AGPL. Blog post here: https://open.dgraph.io/post/licensing/
Comment linking /post/licensing/
on “Cayley – An open-source graph database”Submitted Scale the shit out of this as a story · 12 points
HN discussionSubmitted Running Stack Overflow on Dgraph as a story · 11 points
HN discussionSubmitted Dgraph: Performance of JSON vs. Binary Clients as a story · 10 points
HN discussionSubmitted Show HN: Golang implementation of custom encoding in net/rpc vs. grpc.io as a story · 10 points
HN discussionSubmitted Building a Stack Overflow Clone with Dgraph, and React as a story · 9 points
HN discussionSubmitted Collaborative recommendation engine with Dgraph as a story · 8 points
HN discussionSubmitted Dgraph – Release v0.4 as a story · 7 points
HN discussionSubmitted Build a real-time recommendation engine with GraphQL+- as a story · 5 points
HN discussionSubmitted Dgraph: Text search in a graph DB as a story · 4 points
HN discussionSubmitted SQL vs DGraph as a story · 3 points
HN discussionSubmitted Neo4j vs. Dgraph – The numbers speak for themselves as a story · 3 points
HN discussionSubmitted Golang: Run multiple services on one port as a story · 3 points
HN discussionSubmitted Dgraph Custom Encoding: Go implementation in net/rpc vs grpc & why we switched as a story · 2 points
HN discussionSubmitted Gru: Open source solution for better technical interviews as a story · 2 points
HN discussion
