Hacker News Reader

Comment by dzurico | Hacker News Reader

Hi I can understand your point but if a post is written around a difficult example you need more time to understand it then fully understand what the functionality does. In my case I used a todo because everyone know how to do it and you can appreciate how the use of Hooks can simplify or change your code.

View on HN

Sorry to be PITA. TODO list example wasn't specifically targeted at you. I'm just frustrated because I finished a big migration just Today that was caused by uninformed internet blog posts praising specific library which mostly works only in simple examples (TODO Lists).

Thanks for spreading the knowledge, but I think beginners don't take advice as "this is an option of how things can be done" but rather as "this is how we do things and we should follow this". Maybe a paragraph saying when it makes sense to go for this pattern would help.

Out of curiosity, which library are you referring to?

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...

>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?

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.

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.

You can wrap your root navigator!

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.

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.

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.

nothing involving redux is ever awesome

Hi, I'm a Redux maintainer. Any particular concerns I can help with?

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.

Reply on news.ycombinator.com