4 ms·

1.50 years since app development started 0.75 years since app was released stuck with old version of rn, upgrades break app new team members onboarding takes

• djstein 9y ago
  >stuck with old version of rn, upgrades break app so you have problems you need to sort out with your own codebase. this is not unusual when using any framework. willing to bet this also stems from poor code practices due to the lack of react 'standards' 1.5 years ago / lack of es6+ code >new team members onboarding takes forever, environment is extremely tenuous in terms of onbaording, this is something that can always be improved on. better docs. getting started docs. if you've done it once and realized what new hires are struggling with you can reduce that in the future. the environment isn't really that bad, if you had someone who understands javascript ecosystem then they really only need to know how to bundle the packages through the device specific IDE. just seems like you've got a bad taste in your mouth for a standard everyone else seems to have figured out.
  • whostolemyhat 9y ago
    I had similar issues taking over a project using an older version of React Native. Upgrading is incredibly painful since there's no stable version and libraries don't always update to match. The current release of React Native uses a release candidate version of React, which many of our dependencies haven't yet updated to match, so we're either stuck with an old version with poor compatibility or have to fix dozens of third-party libraries to try to catch up - both are not ideal, and both are caused by constant breaking change releases.