PLEASE READ: We are considering archiving Solidarity, please give feedback!

[jamonholmgren]

@GantMan made Solidarity a few years ago to try to solve the problem of coordinating environments and versions across a broad range of technology -- a problem we have with React Native a lot, since RN has quite an array of languages and tools associated with it.

However, Solidarity doesn't have a big community around it, so we're considering archiving this repo and pointing to alternatives.

If you think Solidarity is still relevant, please tell us! If you don't (but are reading this for some reason), please tell us!

👍 = Yes, archive
👎 = No, don't archive
👀 = I'm just here so I don't get fined

We'd prefer a comment ("why") along with a vote here. The votes are somewhat helpful, but we need to know why you're voting the way you are.

(however, if you see a comment that is essentially what you would have said, just 👍 it)

Thanks for being a part of our open source community here!

[Dannynsikak]

No , don't archive it ,
It's a very vital open source project .
And what I think is lacking now is its popularity around developers
It seems the solidarity is not that popular because developers tend not to know
So I feel with more audience and community,
There is no project that is not relevant to the development community
All we just need if for us devs to be aware of such a software .
Please don't archive it.
Thank you

[flexbox]

Here are my reasons for choosing 👍 = Yes, archive

I have not used it for years now, on React Native stacks because we have:

• npx expo-doctor
• npx react-native doctor
• and rnx-kit

That does the job for me in client's projects as a freelancer.

In terms of machine setup, we are not in 2018-ish anymore.
We even have a node solution to install iOS dependencies with npx pod-install.
I have not encountered "weird bugs" that cause build crashes (and when I do, running npx react-native-clean-project fixes the problem).