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.

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

J2V8 #42

Merged
merged 5 commits into from
Jan 1, 2017
Merged

J2V8 #42

merged 5 commits into from
Jan 1, 2017

Conversation

gliechtenstein
Copy link
Contributor

Switching out JS engine

gliechtenstein and others added 5 commits December 21, 2016 07:04
# Pros
- With AndroidJSCore there was a problem with emoji support and
couldn’t do anything about it since it’s a low level thing. So
previously we used to just “censor” out unicode characters. J2V8
supports emojis (unicode) right out of the box!
- Smaller APK size than AndroidJSCore => Just tried building a signed
APK => It’d 9.8MB. Note that it’s larger than Duktape.
- No problem with regular expressions => This was the top reason I
decided to try J2V8, because Duktape wasn’t able to parse some JS
function calls at all due to its strict regular expression engine

# Cons
- Not much except that it’s larger than Duktape (9.8MB).

# Conclusion
9.8MB is still a significant improvement from 40MB, not to mention: 1.
Performance improvement; 2. Unicode support

Kind of leaning towards J2V8 unless there’s something I’m missing.
@gliechtenstein gliechtenstein merged commit d6777da into develop Jan 1, 2017
@gliechtenstein
Copy link
Contributor Author

HUUUUGE Update! Thanks @brad ! Need to update the parser JS file a bit and then close the issue soon!

@lukeramsden
Copy link
Contributor

@gliechtenstein What sort of difference does this make in terms of apk size and speed?

@gliechtenstein
Copy link
Contributor Author

@lukeramsden It brings the size down from 41MB to 9MB :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants