Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: update FAQ.md #11

Merged
merged 1 commit into from
Mar 5, 2023
Merged

docs: update FAQ.md #11

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions FAQ.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,3 +112,11 @@ as part of the update request. Thus the update server could be written to
respond with either the next incremental version or the latest version depending
on your application's needs. The current demo always sends the latest version
but this logic would not be hard to add.

# Why are some parts of the code push library written in Rust?

Parts of the code push ("updater") system are written in Rust:
1. Avoids starting two Dart VMs (one for the updater and one for the app).
2. Allows accessing the updater code from multiple languages (e.g. both the C++ engine as well as a Dart/Flutter application, or even Kotlin/Swift "native" code if needed)

See our [Languages Philosophy](https://github.com/shorebirdtech/handbook/blob/main/engineering.md#languages) for more information as to why we chose Rust.