Plan to migrate to react@16?

[mastilver]

Plan to migrate to react@16?

[theskillwithin]

would be interested in knowing the answer to this as well

[aickin]

It's also worth noting that React 16 has some features that overlap with Rapscallion:

• Streaming is supported, with the new methods renderToNodeStream and renderToNodeStaticMarkup.
• Server rendering is now a lot faster than it was in React 15.

There are, however, some Rapscallion features that are not in React 16:

• You can not embed a stream in a component, so streaming HTML templating with renderToNodeStaticMarkup doesn't work.
• There is no caching strategy.

[eberhara]

+1

[ScriptedAlchemy]

What about opening a PR with: https://github.com/zackljackson/react-component-caching mapped into the API of rapscallion? Or at least the renderer of it?

@mastilver @aickin @theskillwithin @eberhara any of you guys interested in working together up update it? Possibly taking the render mechanism from : https://github.com/zackljackson/react-component-caching
and retrofitting it into rapscallions API? Even if we lose a few features. Caching and templatization is available in this repo.

Many is better than one :) <3

[ryan-roemer]

Closing in favor of #120 which is most recent discussion of React16 support. (This ticket details the why we need it more, but I think we all agree we need it, so I'm honing us down to one ticket 😛 )