EdgeDB VS Immutable.js

A new DB, with a new query language that's like "SQL done right"? This immediately reminded me of EdgeDB: https://edgedb.com/ Is there anyone here who knows enough about these two products to do a compare/contrast? - Source: Hacker News / 9 months ago

See also https://edgedb.com/ which is another relational database without sql. - Source: Hacker News / 9 months ago

>relational no-sql Do you mean something like edgeDB?[0] Or do you mean some non-declarative language completely? I don't see the latter making much sense. The issue with SQL for me is the "natural language" which quickly loses all intended readabilty when you have SELECT col1, col2 FROM (SELECT * FROM ... WHERE 1=0 AND ... Which is what edgeDB is trying to solve. [0]https://edgedb.com/. - Source: Hacker News / 12 months ago

You have to do your own optimiser to avoid, for instance, the N+1 query problem. (Just Google that, plenty of explanations around.) Many GraphQL frameworks have a “naive” subquery implementation that performs N individual subqueries. You either have to override this for each parent/child pairing, or bolt something on the back to delay all the “SELECT * FROM tbl_subquery WHERE id = ?” operations and convert them... - Source: Hacker News / about 2 years ago

The Immutable.js README has a much more complete description of immutability and why you might want to use the library. Also worth mentioning that Immer is an alternative which is a bit easier to get started with. - Source: dev.to / over 1 year ago

You could create explicitly immutable references and state by using a tool like Immer.js or Immutable.js and do something like your example using their API. Source: almost 2 years ago

There are also libraries such as Immer and Immutable that were created to make our lives easier while dealing with immutability in JavaScript. - Source: dev.to / over 2 years ago

Use persistent immutable data structures (as implemented in, for instance, mori or Immutable.js) to represent the state. As much as possible, push calculations into referentially transparent functions (i.e., input depends purely on output) which take persistent data. Write the interactions with the real world in imperative style. Source: over 2 years ago