3 ms·

https://docs.expo.io/versions/latest/sdk/filesystem https://docs.expo.io/versions/latest/sdk/filesystem

• ItsMe000001 8y ago
  That's not RN but Expo on top of it. We tried Expo and very quickly decided against it. I forgot the reasons, somebody else did it and reported the findings and we all agreed. Besides, why would I add an entire pretty big layer on top of still beta RN (version number well below 1) only to get one tiny component? That only makes sense if one wants the entirety of Expo, and this is where our tester (if we should use it) quickly ran into numerous issues. I understand that it's en vogue to immediately point to this or that npm package or github repo for every problem big or small, but we don't do that. We look at the sources of every package we include, and we look at possible maintenance issues. Our own stuff is trouble enough, we don't need the added problems of all those layers on top of layers of "stuff". I know it's "move quickly and sort it out later when the business has grown" - but we don't want to work like that whenever we can avoid it. Because we don't have an "exit plan", we ourselves will have to maintain the mess we create now...