Conversation

This matches our own analysis almost point for point. We're now building in React Native (though a year behind Artsy's daring timeline!).

Quote Tweet

Artsy Open Source

@ArtsyOpenSource

· Feb 6, 2017

What does a modern @ArtsyOpenSource JavaScript project look like? A longform piece by @orta on a 2017 JS stack

artsy.github.io/blog/2017/02/0

5:58 PM · Feb 6, 2017Twitter for iPhone

Replying to

did you hear the rumblings that react native is on life support at FB?

Andy Matuschak

@andy_matuschak

Feb 6, 2017

That seems pretty clearly untrue; I know many of the team members, and they’re expanding in size + deploying in more places…

Show replies

Replying to

That’s my fault media1.giphy.com/media/kYkQYXkO. It was indeed a tad early, but we were at a point that we had to do it then or not.

Andy Matuschak

@andy_matuschak

Feb 6, 2017

I’m still wincing from the huge damage of adopting Swift in 2014; wanted to let others guinea pig this time. ;)

David He

@davidhexd

Feb 6, 2017

AFAIK, a lot of teams are still going strong with RN

👋🏼

Replying to

Ah, oops, I’d meant to link

@orta

’s analysis of pros/cons to moving to React Native! Though the other’s great too.

Quote Tweet

Artsy Open Source

@ArtsyOpenSource

· Feb 6, 2017

Why did @ArtsyOpenSource move to @reactnative? This longform piece by @orta examines 1 year with React Native

artsy.github.io/blog/2017/02/0

./orta@mastodon.social --degrowth --

@orta

Feb 6, 2017

hah, yeah, I had wondered if you were also making the same JS choices on the other side. Took a long time to settle on them.

Show replies

Scott Raymond

@sco

Feb 6, 2017

we're actually still investing pretty strongly in RN. next up are trials sharing code between native and web.

Replying to

did you merge teams too?

Andy Matuschak

@andy_matuschak

Feb 6, 2017

Sorta. We already had shared-team project team structures; we also have (& still have) tech-stack-sliced team structures.