timeline for project about jsc-android-buildscripts HOT 4 CLOSED

@hey99xx as for the "but not only" statement we've put it there as I can imagine other projects related to react native can benefit from this. This project does not have any dependencies on react native and allows you to use jsc shared library on android with its standard bindings (that is c/c++). We do not plan on providing any wrappers that would allow for using libjsc directly from java/kotlin code as this is outside of the scope of this project. There are also so many ways on how such a binding could be build, and the choice has to be made based on the usecase.

Regarding the question about switching RN to use JSC build with this project our focus now is to ship this with the most recent Expo distribution. Once that's done and if we don't see any issues related to this change we will start the discussion on how and when to update RN with the most recent JSC.

from jsc-android-buildscripts.

From the Expo side, we're looking into including the newer version of JSC with Expo clients in the future and all Expo developers (including if you detach) will just get the new JSC without any changes needed.

from jsc-android-buildscripts.

Then, I assume there's no plan yet to merge back to Facebook react-native's repository, i.e. make them switch from android-jsc to this package.

Are you at any point declare the project stable for other to consume, or is it too risk for now? I see you might still have bugs to figure out, since you have an open issue "Linking errors on Android 4.4".

from jsc-android-buildscripts.

Sounds reasonable. Thanks for addressing both my comments.

from jsc-android-buildscripts.