@WSPMissingPers1 You guys know that only people that are signed into Twitter can see these links right? Even if the https://t.co/WFx09sYq6E link worked only signed in Twitter users could see it.
@kuplasound My regular reminder that your music reaches into my life like nothing else. Paradise and The Past, The Present tracks have especially been soundtracks for my soul recently.
@TaraBull808 I found the study! So it *actually* says 240 people (avg age 70.4) died from the vaccine. Bloomberg states that 12.7 Billion shots were administered by Oct 2022. So your chance of death from the vaccine (if you’re 70) is 1:52,930,000. You’re far more likely to win the lottery.
Godzilla Minus One is a horribly written and directed film. You can’t convince me otherwise and I believe those that like it have all been conned in some way.
Doesn't the SELECT output only include product information? What if I wanted to filter at different points in the query? Something like this:
-›order(filter last 30 days)-›product(filter cost > 50)<-order<-person(filter from US)-›order-›product
this would give an entirely different result from this query:
-›order(filter last 30 days)-›product<-order<-person(filter from US)-›order-›product(filter cost > 50)
Also, I'v read the documentation a few times and I don't see a clear explanation for using a left arrow vs right arrow.
I’ve worked a lot on databases, and I see new ones pop up all the time that are nothing special. @edgedatabase has finally done something moving the space forward in significant ways! https://t.co/L9QCUsgkv4
A computer program cannot be intelligent.
Intelligence requires creativity and a program cannot be creative because its output is pre-determined.
I cannot fathom how people don’t get this.
The foot gun aspect is the way this kind of API hides complexity. When you see a wall of SQL JOINs you know it's a fat ass query and are more likely to handle it appropriately. I don't think a database should make it so easy to write a query that performs 6 joins. It's dangerous.
@Datastorydesign@CanRau@edgedatabase@SurrealDB Hey thanks for the reply! Specifically the graph relation API feels like a foot gun, it's not verbose enough in my opinion. For example, how would I modify the graph query to only get recommendations from orders in the last 30 days?
@Datastorydesign@CanRau@edgedatabase@SurrealDB It seems like in practice you're probably going to end up breaking these down into subqueries to extract the appropriate data at each layer. The fancy graph arrow API really only works for trivial requirements.
@CanRau@edgedatabase@SurrealDB Lots of interesting ideas! While they invited their own query language, it's actually harder to use than SQL in some cases. Who the fuck can make sense of all the arrows below?
@ezsmith397 I'm sure you see this still happening.... How many local businesses treat their internet presence as an afterthought? Small business owners aren't nearly as savvy as they think they are, and they often pay dearly for it.
@ezsmith397 The post COVID world requires a new way of doing business. There are still thriving store fronts, but much the "old guard" that hummed along for the last 50 years got complacent and paid for it.
Marc Andreessen's article on AI Doomerism perfectly encapsulates the way I think about it far more effectively than I ever could. It was kind of surreal to read my own thoughts, developed and communicated better and further than I could take them. https://t.co/Okq0FJPfh0