5 ms·

Specifically: `react-native-navigation` replaced with `react-navigation`. Few issues: - Tons of bugs (see next point) - Bigger error/bug surface, 3 languages

Specifically: `react-native-navigation` replaced with `react-navigation`. Few issues: - Tons of bugs (see next point) - Bigger error/bug surface, 3 languages compared to 1. - Poor documentation - Stopped accepting PRs for 1.0 when they decided 2.0 is the way to go (randomly, 2.0 wasn't nearly ready) - Closing issues without any response (bot that closes them, wtf?) Check Twitter, Google or whatever and people will mostly say positive stuff about it how they are excited and how fun it is for their TODO List app. We tried building something more sophisticated and it's insane how many things don't work as documented. Note: react-navigation is also pretty bad, it improved in last year, but there is nothing better in the react-native ecosystem (there used to be something but during my months of inactivity it was removed from the RN itself). Can probably compile a list of high profile libraries that suck if anyone is interested...

stackola 8y ago
>Can probably compile a list of high profile libraries that suck if anyone is interested Please do! I agree with your stance on react-native navigation, but I'm not having too many problems with react-navigation. What's your issue with it?
- ponyous 8y ago
  Seems like there is interest, will compile and publish to HN in the next couple of weeks. react-navigation is pretty good actually, haven't had any big issues this time. At the beginning when I first evaluated it they had breaking changes way too often, things were buggy, all in all, it wasn't ready for production. Today it feels different, but I can't write a blog post about it yet as I haven't been using it for long enough.
  - com2kid 8y ago
    3.0 has some breaking changes, but hey, they are using semver correctly at least! I'm still not sure how to get previous functionality from 2.0 (app wide background image) working in 3.0, considering that now my root component has to be provided by React-Navigation.
    - stackola 8y ago
      You can wrap your root navigator! <ImageBackground> <RootNavigator/> </ImageBackground> There can be only 1 navigator rendered at a time, but it does not have to be the root of your application. Otherwise there wouldn't be any redux, either.
      - com2kid 8y ago
        Ah ok, the docs didn't make it 100% clear and I got tired messing with the toy app I was using with React Navigation.
- java_script 8y ago
  People already do this, they're those "awesome-react", "awesome-redux", etc GitHub repos with the giant readmes and peppered with emojis. IMO it's kinda mean to sarcastically name them like that.
  - mosdl 8y ago
    nothing involving redux is ever awesome
    - acemarke 8y ago
      Hi, I'm a Redux maintainer. Any particular concerns I can help with?
kall 8y ago
Sure react-native-navigation can be a pain but saying that the only reason to choose it is toy-project articles is a bit harsh. It's really the only choice available if you want to create a react native app with first class accessibility / native interaction. Arguably you should pick native over RN if you care that the VoiceOver back gesture works and Picture in Picture views on iPad are positioned correctly below the navigation bar but react-native-navigation is doing a valuable and difficult thing that no one else is attempting.

stackola 8y ago

>Can probably compile a list of high profile libraries that suck if anyone is interested Please do! I agree with your stance on react-native navigation, but I'm not having too many problems with react-navigation. What's your issue with it?

ponyous 8y ago
Seems like there is interest, will compile and publish to HN in the next couple of weeks. react-navigation is pretty good actually, haven't had any big issues this time. At the beginning when I first evaluated it they had breaking changes way too often, things were buggy, all in all, it wasn't ready for production. Today it feels different, but I can't write a blog post about it yet as I haven't been using it for long enough.
- com2kid 8y ago
  3.0 has some breaking changes, but hey, they are using semver correctly at least! I'm still not sure how to get previous functionality from 2.0 (app wide background image) working in 3.0, considering that now my root component has to be provided by React-Navigation.
  - stackola 8y ago
    You can wrap your root navigator! <ImageBackground> <RootNavigator/> </ImageBackground> There can be only 1 navigator rendered at a time, but it does not have to be the root of your application. Otherwise there wouldn't be any redux, either.
    - com2kid 8y ago
      Ah ok, the docs didn't make it 100% clear and I got tired messing with the toy app I was using with React Navigation.
java_script 8y ago
People already do this, they're those "awesome-react", "awesome-redux", etc GitHub repos with the giant readmes and peppered with emojis. IMO it's kinda mean to sarcastically name them like that.
- mosdl 8y ago
  nothing involving redux is ever awesome
  - acemarke 8y ago
    Hi, I'm a Redux maintainer. Any particular concerns I can help with?

kall 8y ago

Sure react-native-navigation can be a pain but saying that the only reason to choose it is toy-project articles is a bit harsh. It's really the only choice available if you want to create a react native app with first class accessibility / native interaction. Arguably you should pick native over RN if you care that the VoiceOver back gesture works and Picture in Picture views on iPad are positioned correctly below the navigation bar but react-native-navigation is doing a valuable and difficult thing that no one else is attempting.