Well I mean, like, react-navigation has gesture-handler now which already requires a link. Meaning, overall it’s nothing new to have in the readme a Link step
-
-
Yep but think about all tutorials currently written. Things that reference gesture-handler already say to link. Now all tutorials referencing AsyncStorage, or any other lib will now cause errors if people follow them
2 replies 0 retweets 2 likes -
Replying to @browniefed @Kelset and
While this is painful, one of the sayings I think I heard from
@tomocchino is “there will be more React Native code written in the future than there has been up to this point”. We should be the best citizens we can for the community but we shouldn’t be afraid of forward progress2 replies 1 retweet 10 likes -
Replying to @Eli_White @browniefed and
wat. I didn't realize asyncStorage got split out. I get that FB wants less responsibility and surface area in RN, but it's probably going to lead to versioning hell for users over the long run.
2 replies 0 retweets 3 likes -
Replying to @GroundControl @Eli_White and
fwiw this isn't about offloading responsibility, a lean core allows the community to iterate faster on individual modules because they're not tied to the release cycle of core and not blocked on fb
1 reply 0 retweets 5 likes -
Replying to @rickhanlonii @GroundControl and
*that said* at the moment there is not a sustainable“plan” for the maintainers of the offloaded components to keep doing that in the long run. BUT we are discussing solutions to help them. And hopefully
later this year there will be one in place.
#foreshadowing1 reply 0 retweets 4 likes -
Replying to @Kelset @GroundControl and
Isn't this true of every library on npm?
1 reply 0 retweets 1 like -
Replying to @rickhanlonii @GroundControl and
...no...? I’m not sure what “this” should be “true for every library on npm”. And also, that doesn’t mean that it we shouldn’t try to make the situation better. The overall OSS ecosystem has huge sustainability issues.
1 reply 0 retweets 0 likes -
Replying to @Kelset @GroundControl and
Sorry what I mean is that most libraries on npm don't have long term sustainability plans, the contributors could stop at any time Despite this, the system works because people in the community that care about a particular library are able to keep it alive or folk
1 reply 1 retweet 2 likes -
Replying to @rickhanlonii @Kelset and
So sustainability is built into the open source model as long as licensing allows it
1 reply 0 retweets 1 like
I disagree.
The system doesn't work and that's why:
- graphql is now in the Linux foundation
- Babel has an @opencollect
- webpack has one
Etc.
-
-
Replying to @Kelset @rickhanlonii and
And that's also why
@FormidableLabs allows its employee to work on#opensource during working hours - or gives retribution for non-work hours spent doing#OSS. Which is DOPE AF
And more companies should do this.1 reply 0 retweets 1 like - 6 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
- mental health
- 