Thanks @krauser! I'll check this out!

@jeaye Is it a bad idea to use re-natal?

@rovanion what makes you think that?

Apropos his comment https://clojurians.slack.com/archives/C0E1SN0NM/p1506195162000043

ah.. I'd interpret that more as "let's all help fix re-natal issues" 🙂

@drapanjanas does a great job maintaining it IMO

there's a lot of room for improvement of course but re-natal is very usable at this point and up-to-date with react-native

@rovanion I think re-natal is a good way to go.

@rovanion I don't know of a better solution than re-natal right now, so you should definitely use it. As @pesterhazy said, I'm more focused on raising attention about re-natals issues so we can all improve it more.

Multiple design issues are have caused us to insert workarounds in both our workflow and our source code.

@jeaye can you give an example? I'm curious

@pesterhazy https://github.com/drapanjanas/re-natal/issues/133 and https://github.com/drapanjanas/re-natal/issues/112

The former, which shows the forced layout and separation of Android/iOS code is a facade and both are actually run on both devices. The latter, which requires us to keep changes in our index/stash for .re-natal which we can't commit.