Consider using `deps-info` for `neil new` implementation about neil

[borkdude]

@rads Hmm, I already have a library with the same name but with a different purpose: https://github.com/borkdude/deps-infer.

[rads]

@borkdude: Ah, I didn't know about that one! I can change the name if that's the main blocker here.

[rads]

Woops, wrong button!

[rads]

I should clarify that I plan to change the name regardless of whether we use the library for neil. Definitely want to avoid any conflicts with your library.

[borkdude]

On the other hand, borkdude/deps-infer isn't very actively developed and used, so maybe it's not a big deal. Coming up with a good unique name is hard.

[borkdude]

Other than that, I don't see a problem, other than maybe some redundant code in the library which could slow down neil's startup time. I do prefer keeping neil's deps as lean as possible to ensure good startup and bb compatibility.

[rads]

@borkdude:

I do prefer keeping neil's deps as lean as possible to ensure good startup and bb compatibility.

I agree. I think I can keep any extra stuff out of neil by splitting the namespaces and using :deps/root as needed.

[rads]

I've created a duplicate issue of #79 in rads/deps-info#1. This means I can implement the GitLab/Bitbucket/Beanstalk/Sourcehut integration there and both bbin and neil will be able to use it.

Going to hold off on using deps-info for neil until rads/deps-info#1 is done first.