r/reactnative • • Mar 13 '19

News Microsoft's public React Native fork (used to develop Office - supports iOS, Android, macOS, and possibly Windows) has merged another big update (v0.51 -> v0.57)

https://github.com/Microsoft/react-native
63 Upvotes

15 comments sorted by

5

u/legobiker Mar 13 '19

Glad to see a heavyweight get behind a transpiling project, but there might have to be a reckoning in the future to reconcile main branches.

It seems that one of the things a Javascript project loves to do best is fork and scatter efforts..

This branch is 151 commits ahead, 1894 commits behind facebook:master.

2

u/Bamboo_the_plant Mar 13 '19

Yes, catching up with the ever-escaping upstream project is what fatigued the original react-native-macos effort by ptmt. Keeping their multi-platform implementations up-to-date whilst merging from upstream and applying their own patches must be a special kind of hell. I'm sure they welcome the Slimmening/Lean Core movement.

Thankfully, Microsoft are on top of this. They've said that they're using RN for all of their big-hitting commercial products, and they're putting full-time staff on the RN development effort (which react-native-macos, as a community project, was unable to do). It's a monumental task, but they're clearly up for it.

What I wonder about is how things will go in future: surely they don't have the stamina to keep patching from upstream forever? At some point, they'll need to either:

  • convince Facebook to merge repositories

  • convince Facebook to take all platform-targeted sources out of the core;

  • run their own competing fork of RN (which would admittedly be very Microsoft-like...)

2

u/legobiker Mar 13 '19

between facebook, google, and microsoft running their own competing webapp software development ecosystems (react, angular, ...vscode?)

whichever area two decide to cooperate in is a strategic move against the other.

i did a quick search and typescript doesn't seem to be mentioned, so at least for now that isn't being pushed.

clash of titans for now.

1

u/Bamboo_the_plant Mar 13 '19

whichever area two decide to cooperate in is a strategic move against the other.

Although Google's entered the scene with Flutter, I don't see emerging cross-platform tools as a threat to Microsoft's business. I think more that they picked the tool that they felt was the best fit, possibly based on the expertise they had on hand.

i did a quick search and typescript doesn't seem to be mentioned, so at least for now that isn't being pushed.

I'm not convinced the search function is fully working in the repo in any case (it may not be completely indexed or something). I assume they stuck with JS because Facebook aren't dropping JS (nor Flow) anytime soon, and Microsoft have to stick with the language of the upstream repo to make meaningful source merges.

1

u/[deleted] Mar 13 '19

If I understood it right the rn team is making this easier. At least that's what I got from their ama

1

u/Bamboo_the_plant Mar 14 '19

The Lean Core effort, yes. I’m sceptical about how far it’ll manage to go.

3

u/legobiker Mar 13 '19

Facebook (and presumably other companies who opensource libraries) builds the tool for themselves first, and the community second.

I think the community had suffered from a little neglect, from what I had gathered in reading docs, due to Facebook's internal testing pipeline not coming across the pitfalls the community had (lack of FB internal tools, let's say)

The steps they've said in the past year have indicated they do want to be more involved, perhaps they sense that they could gather mind and market share. With the emphasis on closing and merging PR's.

I do enjoy the React ecosystem having had prod experience in Angular, Vue, and React, but I wouldn't want Facebook to be the sole custodian of a "React only" future. (React implementing Hooks, for example, is a little troubling to me from that standpoint)

Microsoft, Facebook, and Google behind a single React Native repo would be extremely beneficial for users and devs..

0

u/[deleted] Mar 13 '19

[deleted]

2

u/Bamboo_the_plant Mar 13 '19

Very true. They're model citizens nowadays. But Facebook are reticent about merging code that may break their internal tests or that concerns features that aren't relevant to their use cases. Microsoft are using RN to develop Office and therefore have very different use cases (likely a greater variety, too). At some point, Microsoft's going to have to do something to ensure that they aren't forever playing catch-up with a partly inferior repo.

6

u/Bamboo_the_plant Mar 13 '19 edited Mar 13 '19

Looks like they merged the changes on March 1st.

Interesting links:

The aforementioned PR mentions the following, which hints at Windows source:

I'll keep fixing up the iOS/Mac merge conflicts and then shift to cross-plat files, but don't have a build environment to build/test Android or Windows, so help would be appreciated there.

Their package.json also mentions the following platforms in their haste settings:

  • ios

  • macos

  • android

  • windesktop

  • uwp

... However, GitHub search is not returning any results for me, so I can't see where they've put their windesktop and uwp sources. There's no top-level ReactWin folder. Maybe it's still private? Or maybe I'm just blind.

After all these organisations backing out of RN, I'm excited to see Microsoft doubling-down on it!

2

u/TheBlackSunsh1ne Mar 13 '19

After all these organisations backing out of RN, I'm excited to see Microsoft doubling-down on it!

Sorry but I'm out of the loop here, why are a bunch of organisations backing out?

2

u/Bamboo_the_plant Mar 13 '19

From this comment chain on the recent AMA, if I'm skim-reading correctly:

  • Udacity

  • Airbnb

  • Capital One

  • Uber

And is Wix still keen on it? Their work has slowed down a lot on React Native Navigation.

2

u/russeg Mar 14 '19

wix navigation still active and they still do post some stuff on medium about rn. but tal kol (the one who does a lot of presentation on rn) has left wix already.

1

u/Noitidart2 Mar 14 '19

I'm still looking for a cross-platform desktop app React Native solution.

1

u/Bamboo_the_plant Mar 14 '19

Well... here it is :) It’s good enough for Microsoft Office!

I’ve been using react-native-macos to make LinguaBrowse for macOS – example video. I then use standard React Native to make it for iOS (and one day, Android). But if I could use Microsoft’s fork, I wouldn’t even have to mix forks to target both platforms.

I did try using Microsoft’s earlier fork, and got RNTester running on macOS – but had issues getting the metro bundled to work properly. Their team told me that it’s because they’d neglected to commit some helper code to the repo. Maybe this time they’ve committed it..!

1

u/Noitidart2 Mar 14 '19

Interesting thanks for sharing that issue and how you contacted MS about those missing commits!