exception-handling

Proposal to add exception handling to WebAssembly (by WebAssembly)

Exception-handling Alternatives

Similar projects and alternatives to exception-handling

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better exception-handling alternative or higher similarity.

exception-handling reviews and mentions

Posts with mentions or reviews of exception-handling. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-11-03.
  • Bring garbage collected programming languages efficiently to WebAssembly
    16 projects | news.ycombinator.com | 3 Nov 2023
    Interesting article, thanks!

    Notes on the issues mentioned there:

    * The need for a manual shadow stack: This is fixed in WasmGC (in the same way it works in JS, as the link mentions).

    * Lack of try-catch: This is fixed by the Wasm exception handling proposal, which has already shipped in browsers, https://github.com/WebAssembly/exception-handling/blob/main/...

    * Null checks: Mostly fixed by WasmGC. The spec defines non-nullable local types, and VMs can use the techniques the article mentions to optimize them using signals (Wizard does, for example).

    * Class initialization: This is a difficult problem, as the article says. J2Wasm and Binaryen are working to optimize it through static analysis at the toolchain level. Here is a recent PR I wrote that makes progress there: https://github.com/WebAssembly/binaryen/pull/6061

    * The vtable overhead issue the article mentions may be a problem. I'm not aware of good measurements on it, through. There are some ideas on post-MVP solutions for method dispatch that might help, but nothing concrete yet.

    * Checks for null and trapping: There has been discussion of variants on the GC instructions that throw instead of trap. Measurements, however, have not shown it to be a big problem atm, so it is low priority.

    The author is right that stack walking, signals, and memory control are important areas that could help here.

    Overall with WasmGC and exceptions we are in a pretty good place for Java as emitted by J2Wasm today: it is usually faster than J2CL which compiles Java to JavaScript. But there is definitely room for improvement.

  • In the latest demo with Dart, WebAssembly and GC in Chrome how was the Exception Handling solved?
    1 project | /r/dartlang | 1 Feb 2023
    It uses https://github.com/WebAssembly/exception-handling/blob/master/proposals/exception-handling/Exceptions.md which is actually supported by all major browsers already.
  • 'The best thing we can do today to JavaScript is to retire it,' says JSON creator Douglas Crockford
    6 projects | /r/javascript | 5 Aug 2022
    Yep, you're right. It's also more than just the DOM, it's web APIs in general, such as fetch, audio, webgl/webgpu, etc. WASM still needs GC, exceptions, and WASI to be able to fully interop with any host without any of the current limitations. This'll take a few years. I'm looking forward to the future in which I will be shipping WASM-only web apps to my users.
  • WebAssembly Everywhere
    4 projects | /r/programming | 25 Jun 2022
    Its a part of the wasm plan to support gc https://github.com/WebAssembly/gc exceptions https://github.com/WebAssembly/exception-handling
  • What's New in Node.js 17
    3 projects | dev.to | 17 Nov 2021
    As of Node.js 17, the v8 JavaScript engine has been updated to v9.5. The changes in this release are primarily aimed at expanding internationalization for dates and calendars as well as for the output of time zones. It also implements the WebAssembly Exception Handling proposal, designed to reduce overhead compared to current JavaScript-based workarounds.
  • WebContainers: Run Node.js natively in the browser
    11 projects | news.ycombinator.com | 20 May 2021
  • Google admits Kubernetes container tech is too complex
    8 projects | news.ycombinator.com | 25 Feb 2021
    Agreed, although at some point in a not very far feature most of those missing features will resolved. So in my mind is just a matter of time. The Wasm Community group is doing an awesome work on that :)

    Here are a few examples of what needs move forward in Wasm:

    * [1] Wasm Exceptions Handling: Right now Wasm is missing a way to handle exceptions natively (C++ programs can only compile to Wasm using the asyncify or longjmp/setjmp tricks via Js try/catch)

    * [2] Wasm GC: Wasm Binary files are quite big (specially in interpreted languages). This is partially caused by the GC being included in the Binary itself. The GC proposal will solve this while also providing faster execution.

    * [3] Wasm 64-bit Memory: currently Wasm can only operate with 32-bit data. In some contexts you may want you operate with more than 4GB of memory (for example, when operating over terabytes of data). The 64-bit memory proposal will solve that.

    [1]: https://github.com/WebAssembly/exception-handling

  • A note from our sponsor - SaaSHub
    www.saashub.com | 24 Apr 2024
    SaaSHub helps you find the best software and product alternatives Learn more →

Stats

Basic exception-handling repo stats
7
142
6.8
12 days ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com