OLD | NEW |
(Empty) | |
| 1 .. _migration: |
| 2 |
| 3 WebAssembly Migration Guide |
| 4 =========================== |
| 5 |
| 6 (P)NaCl Deprecation Announcements |
| 7 --------------------------------- |
| 8 |
| 9 Given the momentum of cross-browser WebAssembly support, we plan to focus our |
| 10 native code efforts on WebAssembly going forward and plan to remove support for |
| 11 PNaCl in Q1 2018 (except for Chrome Apps). We believe that the vibrant |
| 12 ecosystem around `WebAssembly <http://webassembly.org>`_ |
| 13 makes it a better fit for new and existing high-performance |
| 14 web apps and that usage of PNaCl is sufficiently low to warrant deprecation. |
| 15 |
| 16 We also recently announced the deprecation Q1 2018 of |
| 17 `Chrome Apps |
| 18 <https://blog.chromium.org/2016/08/from-chrome-apps-to-web.html>`_ |
| 19 outside of ChromeOS. |
| 20 |
| 21 |
| 22 Toolchain Migration |
| 23 ------------------- |
| 24 |
| 25 For the majority of (P)NaCl uses cases we recommend transitioning |
| 26 from the NaCl SDK to `Emscripten |
| 27 <http://webassembly.org/getting-started/developers-guide/>`_. |
| 28 Migration is likely to be reasonably straightforward |
| 29 if your application is portable to Linux, uses |
| 30 `SDL <https://www.libsdl.org/>`_, or POSIX APIs. |
| 31 While direct support for NaCl / Pepper APIs in not available, |
| 32 we've attempted to list Web API equivalents. |
| 33 For more challenging porting cases, please reach out on |
| 34 native-client-discuss@googlegroups.com |
| 35 |
| 36 |
| 37 API Migration |
| 38 ------------- |
| 39 |
| 40 We've outlined here the status of Web Platform substitutes for each |
| 41 of the APIs exposed to (P)NaCl. |
| 42 Additionally, the table lists the library or option in Emscripten |
| 43 that offers the closest substitute. |
| 44 |
| 45 We expect to add shared memory threads support to WebAssembly in 2017, |
| 46 as threads are crucial to matching (P)NaCl's most interesting use |
| 47 cases. Migration items which assume forthcoming threads support |
| 48 are marked below. If your application's flow control relies heavily on blocking |
| 49 APIs, you may also find threads support is required for convenient porting. |
| 50 |
| 51 While we've tried to be accurate in this table, |
| 52 there are no doubt errors or omissions. |
| 53 If you encounter one, please reach out to us on |
| 54 native-client-discuss@googlegroups.com |
| 55 |
| 56 .. contents:: |
| 57 :local: |
| 58 :backlinks: none |
| 59 :depth: 2 |
| 60 |
| 61 PPAPI |
| 62 ----- |
| 63 .. raw:: html |
| 64 :file: public.html |
| 65 |
| 66 IRT |
| 67 --- |
| 68 .. raw:: html |
| 69 :file: public.html |
| 70 |
| 71 PPAPI (Apps) |
| 72 ------------ |
| 73 .. raw:: html |
| 74 :file: apps.html |
OLD | NEW |