isoos

> I am now wondering if anyone has done a graph db where the edges are embedding vectors rather than strict terms.

Curious: how would you imagine it working if there were such a graph db?

Modern, but sane syntax (readable), good defaults (strong typing, null safety...), good-enough runtime performance, good APIs and tooling out of the box, cross-platform (also hot-reload on some, AOT). The list goes on, what specifics do you care about more?

Basho team was very kind to open source contributions in ~2011-12: I've written an open source Riak client in Dart, and they had sent me t-shirts (the quality ones that are rare today). Nice treats for a fun project :)

One of the postgresql client packages (posgres) is roughly 8 years old. That's how "client side" it ever was...

It sounds like you need a desktop workstation with replaceable extension cards, and not a mostly immutable laptop, which has different strengths.

Clearly not all, that would be a different announcement.

Why do you think it must be one thing or the other? It can be better than Javascript, used for Flutter and app development, and also cross-platform compiled and used for backend.

Nit: Approval voting (yes/no for each candidate) is easier to implement and also understand. I couldn't rank 82 people, but could yes/no them...

Note: the title is missing "unless the open source model evolves".

Is your work open source?

I remember a similar read. I think it also helped that armies become more disciplined, could march longer (coffee was a stimulant vs. alcohol), also the workforce had fewer errors. Any chance that somebody knows the reference?