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

What features will Aftman have over Foreman? #1

Closed
Dekkonot opened this issue Aug 24, 2021 · 2 comments
Closed

What features will Aftman have over Foreman? #1

Dekkonot opened this issue Aug 24, 2021 · 2 comments

Comments

@Dekkonot
Copy link

Other than the obvious benefit of not being owned by Roblox (who seem to have no interest in maintaining Foreman), what will Aftman have over Foreman?

I believe you answered this on Discord already but for posterity it should be recorded on GitHub too.

@LPGhatguy
Copy link
Owner

I should turn this into the README at some point.

I'm hoping to fix some of the core design mistakes I made in Foreman and also take a little more care with the codebase. Roughly:

  • Exact version dependencies. Using a range here has tripped up lots of users and I realized at some point that this isn't great.
  • Commands to install, uninstall, and upgrade tools. Editing your global, tucked-away toml file is rough.
  • Change model to no longer trust-by-default. Aftman will prompt before downloading new tools. (Warn for untrusted sources? Roblox/foreman#16).
  • Different strategy for storing executables. (Executable names are weird Roblox/foreman#11)
  • Better heuristics for picking the right artifacts for your platform. Compiler, OS, architecture, plus custom patterns. (Better artifact choosing algorithm Roblox/foreman#18)
  • Proper error handling. I used unwrap all over because Foreman was meant to be a prototype. This should make diagnosing issues a lot easier.
  • Less Roblox-angled. I think that this sort of tool would be useful in general, not just for the Roblox community, so I want to avoid making it overtly Roblox.

@LPGhatguy
Copy link
Owner

The README has since been updated with this information, so I'm going to close this issue.

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