Sigh... nx is already a (well known) thing in the dev space.
/s
I think the fact that a popular github repo (https://github.com/nrwl/nx), a domain (https://nx.dev/), and loads of blog posts and tutorials exist for the current NX is enough reason to pick something else. Just thinking off the top... how about NeX.
Elixir’s documentation is so good, however, I would expect most questions will be answered by the documentation directly.
It's like with trademarks: you can have more than one thing with the same name and not have a problem. If it was another build tool that helped you deal with your git repos that would be a real issue, but it's not... it's aimed at a totally different audience for a totally different reason.
This town is absolutely big enough for the both of them.
Or do you think other people have problems because when they search for, say, Kafka, or Jekyll, they keep finding references to literature instead of the tech they're using?
I use nx.dev and hope they see it the same way.
Picking a (short, memorable) name without colliding with some obscure open source project is neigh-impossible.