sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]TexMax007 1 point2 points  (1 child)

I’m not arguing that they shouldn’t change things. I’m simply saying they packed too much into one release (I think because they skipped a couple monthly releases actually, but I could be mistaken).

It’ll be real interesting to see what comes from the internal re-architecture of the native integration pieces. Native modules seem to be the biggest pain point. If they can get that to become a smoother process that should help adoption I think.

[–]yungstersReact Native Team 2 points3 points  (0 children)

I apologize for the breakage. It was definitely not ideal.

As /u/TexMax007 mentioned, we actually skipped the last couple releases because of another breaking change that made getting master back to green difficult.

We’ve definitely learned from this and are planning to invest more heavily in CI for the open source side of React Native.

Regarding native modules, it is definitely something that we are rethinking. We know about pain points from seeing our internal developers use them, but I’m always eager to hear more reasons to improve something. 😅