GraphQL was designed to add types and remote data fetching abstractions to a large existing PHP server side code base. Cypher is designed to work closer to storage, although there are many implementations that run cypher on top of anything ("table functions" in ladybug).
Neo4j's implementation of cypher didn't emphasize types. You had a relatively schemaless design that made it easy to get started. But Kuzu/Ladybug implementation of cypher is closer to DuckDB SQL.
They both have their places in computing as long as we have terminology that's clear and unambiguous.
Look at the number of comments in this story that refer to GraphQL as GQL (which is a ISO standard).
"he fact that someone can pull up an example where a union caused a business to go under doesn't make me think "we should eliminate unions""
It seems here it does.
For years every time a company fails that also happened to have a union, the union gets blamed. Never mind the management decision.
It's just a common flame bait for some groups to hate unions. That group doesn't actually reasonably think out these things.
It's like 'woke', the word 'union' is a key word that some groups use to label others for hate. They aren't sitting back and making an economic argument.
Like with full time employed Walmart employees that qualify as homeless. Are they happy because they have a job, since poor old Walmart might go under if they were forced to pay a real salary?
There are movie flops, yet also there is an actors union. Workers are allowed to be paid even if management makes bad decisions. The company can go bankrupt, doesn't mean workers shouldn't get paid.
Are being wages owed here? If so, the company either can't pay them, and should be considered bankrupt, or is unlawfully holding them back, in which case they should be sued.
The parent was implying a common argument that a union will drive a company out of business. I'm saying, if there are poor decisions that drive a company out of business, then employees should still be paid. It doesn't make sense that employees should prop up the company by taking a pay cut.
How much of this is just because the market as a whole is going up.
This same kind of mentality happened pre-2008. People thought they were great at being day-traders, and had all kinds of algorithms that were 'beating the market'.
But it was just that the entire market was going up. They weren't doing anything special.
Once the market turned downward, that was when it took talent to stay even.
But the other graph query language "Cypher" always seemed a lot more intuitive to me.
Are they really trying to solve such different problems? Cypher seems much more flexible.
reply