5 ms·
Sigh... nx is already a (well known) thing in the dev space. https://nx.dev/ https://nx.dev/
by JamesSwift 6y ago
Sigh... nx is already a (well known) thing in the dev space.
https://nx.dev/ https://nx.dev/
- deleted 6y ago[deleted]
- ashton314 6y agoI think just slapping “elixir” at the beginning of the search query will help with the discoverability. Maybe if it gets consistently marketed as “Elixir Nx”, this won’t be a problem. Elixir’s documentation is so good, however, I would expect most questions will be answered by the documentation directly.
- JamesSwift 6y agoI agree, adding elixir is the likely solution, but my point is "why?". There's no reason to start off on that foot on day 1. And right now is still day 0 so there is still time to rethink it.
- ljm 6y agoWhat if they did think about it and decided they still wanted to stick with their preferred name? 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?
- bcardarella 6y agoSigh... another Sigh... complaint on HN about naming... sigh... <head desk> Thank you for sigh... pointing out sigh... the obvious sigh...
- Kototama 6y agoI'm looking forward to use Nx with Nix!
- sjtgraham 6y agoYea, I totally agree. We should just stop naming things at this point and just assign everything a UUID v4 label instead. /s
- JamesSwift 6y agoIts about preventing unnecessary friction while its still entirely avoidable. Yes, naming things is hard but renaming things after the fact is _way_ harder. Nothing exists for Numerical Elixer right now, so now is the perfect time to make the change. I think the fact that a popular github repo (https://github.com/nrwl/nx https://github.com/nrwl/nx), a domain (https://nx.dev/ 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.
- daya 6y agoNeX could be the next Elixir
- benatkin 6y agoThere are multiple namespaces within the dev space, and I see no conflict here. I use nx.dev and hope they see it the same way.
- crad 6y agoWell known in the NodeJS community perhaps - outside of that?
- mikl 6y agoI’m a dev, even working in the JavaScript space, never heard of it, so it can’t be that well-known. Picking a (short, memorable) name without colliding with some obscure open source project is neigh-impossible.