I’m currently using a graph database (dgraph) mostly so I can easily query complex relationships), and I’m wondering whether EdgeDB has similar performance due to how it stores data?

my understanding of EdgeDb is that it stores everything in a single table, and there’s an underlying graph structure. does this give added performance on complex queries?in other words, does EdgeDB perform complex queries involving multiple relationships better than an equivalent complex Postgres JOIN query? how does the performance compare to the average graph database for queries involving complex relationships? has it been performance tested on complex queries?

In my opinion, what Twitter is most useful for is sharing links and short updates to prompt action from your followers, like reading your new blog post. And because of this, it's not the kind of place where you want to spend a lot of time, because the content isn't that engaging, it's just the news ticker that you scroll through for 5 minutes and leave.

Personally I think we need a way to measure our health rather than tracking metrics that can encourage unhealthy relationships with our bodies. Ideally we would be able to quickly assess how close we are to a healthy level of body fat, lean muscle mass, be it is too high or too low. Measuring how heavy / big you are feeds into "weight status" and "thigh gap" fixation. In a less-imperfect world we'd be competitive about how healthy we are, rather than silly and often unhealthy things like thinness, and weight.

+ Full stack Ruby on Rails developer

http://benw.me

https://github.com/benwoodward

Ben Woodward

Full stack Ruby on Rails developer. Interested in working with startups and small companies / teams.

Currently booked, but interested in making contacts, future opportunities.

http://benw.me