When to use Babylon Native #1035
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…others yet, of the 'When to Use Babylon Native' docs page.
|
This pertains to #1017, by the way. |
bghgary
reviewed
Mar 23, 2022
There was a problem hiding this comment.
I like it overall. I think I want to see some kind of chart or a graph summarizing the pros and cons of each choice. I would expect this to evolve. For example, we make no mention of the performance issues on iOS without JIT that probably should be mentioned as a consideration.
bghgary
reviewed
Mar 25, 2022
bghgary
approved these changes
Mar 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Somewhat fuzzy documentation page discussing current thinking about when Babylon Native technologies are the "right" choices for making an app. This is of course pretty speculative and will likely evolve significantly as the technologies evolve; but as a starting point, I think this is about where the conversation is right now. Let's discuss!