EngVagabond

Does that automatically run against every PR? What mitigations did you have to put in place for Google security to allow running untrusted code from PRs on internal CI?

Disclaimer, I’m one of the EMs for React at Meta, and spent many years directly working on React Native.

> It is not useful, at all for building apps. Apps (as in, mobile apps) cannot be rendered on the sever. You need an api.

Yet.

React Server Components as a pattern and paradigm are not unique to web sites and the team has designed it with React Native in mind. We are just starting with web to flesh out the ideas and work with the ecosystem first.

RSCs (and SSR) are both technologies totally possible to use with RN, theoretically, we just haven’t built out the support yet. At the most basic, instead of rendering to HTML that the server sends down, it would render to commands that React Native’s native code would execute. Similar to the distinction between React DOM and React Native.

So we are excited about these technologies even though they are currently web only, and it’ll still be a while until we bring them to React Native.

Evan Bacon from Expo also experimented with RSC for React Native: https://x.com/baconbrix/status/1629909713910480898?s=46

As I understand it, Android, the underlying system doesn’t provide support for shadows beyond setting elevation. https://developer.android.com/training/material/shadows-clip...

React Native’s first principle is meeting user’s expectations of the platform. https://reactnative.dev/blog/2020/07/17/react-native-princip...

Since the platform doesn’t provide shadow support, React Native can’t provide that support on Android either. React Native’s shadow API works for the platforms that do support it, like iOS, Windows, and macOS.

Disclaimer: I work on React Native.

Check out the new error screen (LogBox) in 0.63! https://reactnative.dev/blog/2020/07/06/version-0.63

I'm on the React Native team and if this is still an issue, we still want to know about it. As others said, the icebox occurs automatically after a period of inactivity.

From quick glance, this seems more related to Metro, the packager that React Native uses. It was split out from the React Native repo and the team working on it is extremely receptive. I'd recommend opening a new issue on https://github.com/facebook/metro and linking to the issue in the RN repo.

I'm on the React Native team and focusing on testing. Can you elaborate on your experience with testing and what you'd like to see?

It uses Google Drive for cloud file storage (syncing and sharing)

Here is a collaborative file that people have affectionately named Bikini Bottom Dinosaur. Check it out for an example. :) http://thesavior.github.io/draw/#0B9XIM4D3BWcWOU44bzVmNWJSd1...

He has commented below that the 'front end is GWT, back end is Java servlets. Database was originally MySQL but switched to Prevayler for performance reasons.'

I have built a similar tool that is also an HTML5 / Canvas collaborative drawing app which uses Google Drive for storage and has no server code beyond that. It works offline (and syncs up with collaborators when you come online) and runs in Chrome, Firefox, Safari, iOS, and Android and supports touch. http://thesavior.github.io/draw/

This is another HTML5 / Canvas collaborative drawing app that I built which uses Google Drive for storage and thus runs completely locally. Works offline and runs in Chrome, Firefox, Safari, iOS, and Android and supports touch. http://thesavior.github.io/draw/