Replace mttv8 with V8, or offer V8 as an option.

[tchigher]

1. The size of mttv8 has no advantage over V8.
2. Some large apps have already embeded V8, thus doubling the size (V8 and mttv8 together) if Hippy is introduced.
3. V8 is opensource but mttv8 is not.
4. V8's roadmap is public and updates more often and has a larger community than mttv8.
5. V8 now supports iOS(with jit-less on) but mttv8 can't keep up with this feature soon enough.
6. If replacement is not possible due to the fact that this framework is mainly used by Tencent apps, then perhaps you guys can make V8 an option, together with mttv8, and let the users decide which one to use.

[xuqingkuang]

YES, a portable runtime is on the way, you may write the Hippy app with Dart or Lua in the future.

But most recently, the mttv8 from the X5 engine is the best and the only choice runtime, X5 is always following Chromium update, it's based on Chromium 66 currently(will update to Chromium 77 soon), and have a lot of optimized for Hippy.

1. The size of mttv8 has no advantage over V8.

It's because mttv8 built for Android 4.0, it's the lowest Android version that Hippy support also.

[tchigher]

2. Some large apps have already embeded V8, thus doubling the size (V8 and mttv8 together) if Hippy is introduced.

But most recently, the mttv8 from the X5 engine is the best and the only choice runtime

So it seems like a problem that can't be solved in the near future...

[xuqingkuang]

1. Some large apps have already embeded V8, thus doubling the size (V8 and mttv8 together) if Hippy is introduced.

But most recently, the mttv8 from the X5 engine is the best and the only choice runtime

So it seems like a problem that can't be solved in the near future...

sad ...

[sandys]

@xuqingkuang sorry to ask this question again - but is it possible to replace mttv8 with standard v8 and get hippy to work ?

even if it means lowered performance + increased size ?