atl/android_translation_layer
0
0
Fork 0
mirror of https://gitlab.com/android_translation_layer/android_translation_layer.git synced 2025-10-27 11:48:10 -07:00
Code Issues Packages Projects Releases Wiki Activity

FAQ: fix formatting

Mis012
2024-05-07 16:56:13 +00:00
parent aa0cd9fe9b
commit f527ee8c2f
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
FAQ.md

@@ -1,7 +1,7 @@
#### fair, anticipated questions:
**Q**: why Gtk?
**Q**: why Gtk?
**A**: The right tool for the job would probably be some meta-toolkit, so that what we're doing with it would be an intended usecase. That being said, Gtk is a popular, mature, well-maintained project with a C interface (in fact, it's written in C), and above all we think having android apps be Gtk apps is cool and this cool factor could (we hope) attract contributors
**Q**: I don't care if this is cleaner than running an entire AOSP system in a container, are there any tangible benefits?
**Q**: I don't care if this is cleaner than running an entire AOSP system in a container, are there any tangible benefits?
**A**: our design allows for fast start-up time (there's also still room for improvement) and low RAM usage, and it also makes it easy to do stuff like make apps using OpenXR use the system openxrloader and therefore use a regular Linux build of Monado as the OpenXR implementation. Modding is also easier, as is debugging.