JIT-Less V8

#1

Post by bpasero » Wed, Mar 13, 2019, 10:50 AM UTC

Re: JIT-Less V8

#2

Post by ape4 » Wed, Mar 13, 2019, 11:45 AM UTC

"V8 is Google’s open source high-performance JavaScript and WebAssembly engine, written in C++." from its home page. I didn't immediately know

Re: JIT-Less V8

#3

Post by la_fayette » Wed, Mar 13, 2019, 11:51 AM UTC

This means react native can use V8 on iOS? Does this have any consequences on performance or similar?

Re: JIT-Less V8

#4

Post by michaelcampbell » Wed, Mar 13, 2019, 11:58 AM UTC

ape4 wrote: post #2

"V8 is Google’s open source high-performance JavaScript and WebAssembly engine, written in C++." from its home page. I didn't immediately know

And?

Re: JIT-Less V8

#5

Post by mikepurvis » Wed, Mar 13, 2019, 12:01 PM UTC

la_fayette wrote: post #3

This means react native can use V8 on iOS? Does this have any consequences on performance or similar?

Both the rationale and some first-level benchmarks are given in the article.

Re: JIT-Less V8

#6

Post by oso2k » Wed, Mar 13, 2019, 12:11 PM UTC

la_fayette wrote: post #3

This means react native can use V8 on iOS? Does this have any consequences on performance or similar?

Yes. Says so in blog post.

Re: JIT-Less V8

#7

Post by sercand » Wed, Mar 13, 2019, 12:12 PM UTC

la_fayette wrote: post #3

This means react native can use V8 on iOS? Does this have any consequences on performance or similar?

I think JavascriptCore is more performant than V8. So, it is not necessary.

Re: JIT-Less V8

#8

Post by irrational » Wed, Mar 13, 2019, 12:16 PM UTC

Apple requires browsers on iOS to use the same rendering engine as Safari, but would it allow a browser to use a different JavaScript engine? Or is this a loophole that Apple didn't forsee that they will be closing in the future? Are the rendering engine and JavaScript engine so separated that you could use the Safari rendering engine, but a different JS engine?

Re: JIT-Less V8

#9

Post by detaro » Wed, Mar 13, 2019, 12:17 PM UTC

irrational wrote: post #8

Apple requires browsers on iOS to use the same rendering engine as Safari, but would it allow a browser to use a different JavaScript engine? Or is this a loophole that Apple didn't forsee that they will be closing in the future? Are the rendering engine and JavaScript engine so separated that you could use the Safari rendering engine, but a different JS engine?

No, the two are deeply linked and you don't have the kind of access you need to replace it.

Re: JIT-Less V8

#10

Post by andy_ppp » Wed, Mar 13, 2019, 12:20 PM UTC

Does this avoid some of the issues with Spectre et al?