Goodbye PNaCl, Hello WebAssembly!

312 views
Skip to first unread message

Bradley Nelson

unread,
May 30, 2017, 8:20:35 PM5/30/17
to Native Client Discuss
Historically, running native code on the web required a browser plugin. In 2013, we introduced the PNaCl sandbox to provide a means of building safe, portable, high-performance apps without plugins. Although this worked well in Chrome, it did not provide a solution that worked seamlessly across all browsers.

Since then the web community has rallied around WebAssembly, as a cross-browser solution to high performance code. WebAssembly provides the speed necessary to build an in-browser video editor or run a Unity game at a high frame rate utilizing existing standards-based web platform APIs. Applications using WebAssembly already run in multiple browsers: Chrome and Firefox support WebAssembly natively and Edge and Safari support WebAssembly in preview versions of their browsers.

Given the momentum of cross-browser support, we plan to focus our native code efforts on WebAssembly going forward. We will remove support for PNaCl in the first quarter of 2018 everywhere except inside Chrome Apps and Extensions. We believe that the ecosystem around WebAssembly makes it a better fit for new and existing high-performance web apps, and that usage of PNaCl is sufficiently low to warrant deprecation.

We recognize that technology migrations can be challenging. To help ease the transition we have prepared a set of recommendations for existing PNaCl implementations to migrate to the web platform, as well as a feature roadmap for WebAssembly. As you embark on the migration process, please let us know if you run into any challenges, so that we can help make the shift as smooth as possible.

With the launch of WebAssembly, the web platform has gained a foundation for a new generation of fast and immersive web apps that run in any browser. We’re excited to see what developers build next!

Brad Nelson, Software Engineer on NaCl, PNaCl, and WebAssembly

Bradley Nelson

unread,
May 30, 2017, 8:33:30 PM5/30/17
to Native Client Discuss

Bradley Nelson

unread,
May 30, 2017, 8:36:07 PM5/30/17
to Native Client Discuss

Bradley Nelson

unread,
May 30, 2017, 8:39:04 PM5/30/17
to Native Client Discuss

Bradley Nelson

unread,
May 30, 2017, 9:58:37 PM5/30/17
to Native Client Discuss
Message has been deleted

Miroslav Kravec

unread,
Jun 3, 2017, 9:47:16 AM6/3/17
to Native-Client-Discuss
 Bad new. I really liked idea of PNaCL! I had plans to use it in my project... but, now I have to search for an alternative, which I might never find.

Imran

unread,
Jun 3, 2017, 12:55:04 PM6/3/17
to Native-Client-Discuss
Hi Bradley,

Will PNaCl continue to work in Chrome extensions for at least the next two years?

This page seems to only mention Chrome apps, not extensions:

thanks,
imran

Kris Cruickshank

unread,
Jun 12, 2017, 10:33:13 AM6/12/17
to Native-Client-Discuss
I am not sure if I should post here or higher up, but this post triggered my higher up question: https://groups.google.com/forum/#!topic/native-client-discuss/yj3H7PiPdps 

송정희

unread,
Jun 18, 2017, 9:43:24 PM6/18/17
to Native-Client-Discuss
Hi Bradley
I'm roya, I 'm develope for vehicle infortainment.
my company is base on google content_shell,make more simple and more faster car browser .
and one more important work, it is develope  content_shell and native (car side) communication  by Javascript.
we are communicate native by NPAPI, but it is not support, we analyzing ppapi and ppapi plugin part for native plugin support.

but now, google decide not support of PNacl.
I wonder  ppapi/pp plugin part  will be remove with PNacl.

I will be waiting for your reply =) 
Thank you 


 
PNacl will be deprecated... what about Nacl / ppapi / ppapi plugin ? is it disable too?

2017년 5월 31일 수요일 오전 9시 20분 35초 UTC+9, Bradley Nelson 님의 말:
Reply all
Reply to author
Forward
0 new messages