is there a difference between atomFamily default and selectorFamily get?

Was a bit confused by this two approaches.

const userInfoQuery = atomFamily({
    key: 'UserInfoQuery',
    default: async userID => {
        const response = await myDBQuery({userID});
        return response;
  });

and

const userInfoQuery = selectorFamily({
    key: 'UserInfoQuery',
    get: userID => async () => {
        const response = await myDBQuery({userID});
        return response;
    },
});

They both will be recomputed if we pass new userID. So if we don’t need get or set then we can use atomFamily?

[drarmstr]

Both expose the same interface and both may be read/writeable (if the selector provides a set).

Atoms represent and maintain state while selectors represent functions. Use atoms when you need state and a selector when it is derived from other state or async requests.

In reality, atoms with asynchronous defaults are actually implemented by wrapping with a selector. It’s provided as a convenience. So, to your original question, the atomFamily would actually construct selectors to get the async data as well as atoms with state that then go unused if you never set the atom.

[alexandrzavalii]

@drarmstr hmm interesting. In the docs we have this selector

const userNameQuery = selectorFamily({
  key: 'UserName',
  get: (userID) => async ({get}) => {
    const response = await myDBQuery({userID});
    if (response.error) {
      throw response.error;
    }
    return response.name;
  },
});

It was missleading to see the get there even though it is not used. Would it be okay to remove it? Have this pr here: https://github.com/facebookexperimental/Recoil/pull/234