Treasury vs Vault: looking for your opinions about treasury

[MrIvanPlays]

All good.

[creatorfromhell]

Reserve should be removed from this list. It was never designed to be a long-lasting API and more of a stop-gap until something new came along. I think there's this misconception that it's Treasury going up against Vault and Reserve, while I'd rather have Treasury take over the battle because a) I've spent a total of 2 hours working on Reserve so it's not really going to be worth it anyways and b) it gives me more time to focus on better things than constantly responding to messages in regards to Reserve. I fully support Treasury and if it gets adoption I'll add support for it into TNE, but there's no real battle going on, because as I said, Reserve wasn't built to be a long-term API just a stop-gap until something new, or Vault adds the needed methods to their project for multi-currency support.

[MrNemo64]

Treasury has the best documentation of the three projects. Vault's is okay, but it is also missing some key information. Reserve's Wiki is poor, but its javadocs are decent at least.

This doesnt seem to parse correctly

On the BankAccount section

Vault's bank accounts require an owner which is not suitable for all implementations. (...). Vault's require an owner.

Why say it twice?

That's all I could think of right now

[lokka30]

Treasury has the best documentation of the three projects. Vault's is okay, but it is also missing some key information. Reserve's Wiki is poor, but its javadocs are decent at least.

This doesnt seem to parse correctly

On the BankAccount section

Vault's bank accounts require an owner which is not suitable for all implementations. (...). Vault's require an owner.

Why say it twice?

That's all I could think of right now

Thanks, will edit now.

[lokka30]

Reserve should be removed from this list. It was never designed to be a long-lasting API and more of a stop-gap until something new came along. I think there's this misconception that it's Treasury going up against Vault and Reserve, while I'd rather have Treasury take over the battle because a) I've spent a total of 2 hours working on Reserve so it's not really going to be worth it anyways and b) it gives me more time to focus on better things than constantly responding to messages in regards to Reserve. I fully support Treasury and if it gets adoption I'll add support for it into TNE, but there's no real battle going on, because as I said, Reserve wasn't built to be a long-term API just a stop-gap until something new, or Vault adds the needed methods to their project for multi-currency support.

Thanks for the clarification, I assumed it would be a long-term API. Reserve will not be referenced anywhere on Treasury's pages now. 👍🏻

[lokka30]

I am satisfied with the state of the page so I will close this issue. Feel free to leave any more comments, I am just discarding it from our priorities.

[MrNemo64]

There is a typo at the bank account section

reasury's bank accounts have none of these issues.

[lokka30]

There is a typo at the bank account section

reasury's bank accounts have none of these issues.

Good catch! I also found I did not mention the bank permissions system. Fixed both 👍

[creatorfromhell]

Reserve should be removed from this list. It was never designed to be a long-lasting API and more of a stop-gap until something new came along. I think there's this misconception that it's Treasury going up against Vault and Reserve, while I'd rather have Treasury take over the battle because a) I've spent a total of 2 hours working on Reserve so it's not really going to be worth it anyways and b) it gives me more time to focus on better things than constantly responding to messages in regards to Reserve. I fully support Treasury and if it gets adoption I'll add support for it into TNE, but there's no real battle going on, because as I said, Reserve wasn't built to be a long-term API just a stop-gap until something new, or Vault adds the needed methods to their project for multi-currency support.

Thanks for the clarification, I assumed it would be a long-term API. Reserve will not be referenced anywhere on Treasury's pages now. 👍🏻

While it does occasionally get updates, no it's not designed to be a long-term API currently.

[MrIvanPlays]

Reserve should be removed from this list. It was never designed to be a long-lasting API and more of a stop-gap until something new came along. I think there's this misconception that it's Treasury going up against Vault and Reserve, while I'd rather have Treasury take over the battle because a) I've spent a total of 2 hours working on Reserve so it's not really going to be worth it anyways and b) it gives me more time to focus on better things than constantly responding to messages in regards to Reserve. I fully support Treasury and if it gets adoption I'll add support for it into TNE, but there's no real battle going on, because as I said, Reserve wasn't built to be a long-term API just a stop-gap until something new, or Vault adds the needed methods to their project for multi-currency support.

Thanks for the clarification, I assumed it would be a long-term API. Reserve will not be referenced anywhere on Treasury's pages now. 👍🏻

While it does occasionally get updates, no it's not designed to be a long-term API currently.

Looks more like an API which is made for private use rather than an actual API. No bad feelings though.

[lokka30]

@MrIvanPlays

It was never designed to be a long-lasting API and more of a stop-gap until something new came along.

🙂