While we’ve tried to be accurate in this table, there are no doubt errors or omissions. If your application’s flow control relies heavily on blocking APIs, you may also find threads support is required for convenient porting. ![]() Migration items which assume forthcoming threads support are marked below. We expect to add shared memory threads support to WebAssembly in 2017, as threads are crucial to matching (P)NaCl’s most interesting use cases. Additionally, the table lists the library or option in Emscripten that offers the closest substitute. We’ve outlined here the status of Web Platform substitutes for each of the APIs exposed to (P)NaCl. For more challenging porting cases, please reach out on native-client-discuss. While direct support for NaCl / Pepper APIs in not available, we’ve attempted to list Web API equivalents. Migration is likely to be reasonably straightforward if your application is portable to Linux, uses SDL, or POSIX APIs. Toolchain Migrationįor the majority of (P)NaCl uses cases we recommend transitioning from the NaCl SDK to Emscripten. ![]() We also recently announced the deprecation Q1 2018 of Chrome Apps outside of ChromeOS. This change is not intended to affect NaCl or PNaCl in Chrome Apps or extensions, and the “enable-nacl” flag in chrome://flags can also be used to enable PNaCl locally for testing (this flag also retains its current function of enabling non-PNaCl “native” NaCl on any page). The trial is scheduled to last through Chrome 78, approximately until December 2019. A developer can register on the Origin Trial Console and receive a token, which can be embedded into a page and will enable the feature without the user needing to use a flag. This is usually a new proposed feature but in this case it’s a feature being deprecated. ![]() We believe that the vibrant 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.Īs of Chrome 76, PNaCl on the open web has been moved behind an Origin Trial, which is a mechanism for web developers to register and get access to a feature that isn’t on by default. Given the momentum of cross-browser WebAssembly support, we plan to focus our native code efforts on WebAssembly going forward and plan to remove support for PNaCl in Q4 2019 (except for Chrome Apps).
0 Comments
Leave a Reply. |