Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardization: Environment storage and/or/xor switching mechanism? #20

Closed
marcelklehr opened this issue Jan 5, 2018 · 1 comment
Closed

Comments

@marcelklehr
Copy link
Member

I perceive environment storage (i.e. where node, npm, etc. go) to be very distinct and separable from the actual switching mechanism.
From what I can tell, it is probably far easier to standardize "where node (and everything related) can be found" in the file system, rather than standardize all the switching scopes (see #4) and mechanisms to implement them.

I would thus suggest to primarily focus on standardizing the former., the idea being: the backend stays the same, while you can switch the front end (your version manager) seamlessly, and even, if that's technically possible without conflicts, have multiple interfaces to the backend, i.e. manage versions with different prorgrams at the same time.

What do you think?

@ljharb
Copy link
Member

ljharb commented Jan 7, 2018

Agreed; this is a duplicate of #3.

@ljharb ljharb closed this as completed Jan 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants