3 ms·

I agree, that's the thought I've had ever since learning of native client. These native, proprietary solutions have come and gone, such will be the fate of NaCl

by pvnick 13y ago

I agree, that's the thought I've had ever since learning of native client. These native, proprietary solutions have come and gone, such will be the fate of NaCl. As far as I'm concerned the future of high-performance webbrowser computing will be javascript-based through projects like asm.js or remote cloud architectures (eg https://brendaneich.com/2013/05/today-i-saw-the-future/ https://brendaneich.com/2013/05/today-i-saw-the-future/)

axelf 13y ago
How is this proprietary? Isnt there an open spec?
- cpeterso 13y ago
  Is there a PNaCl spec or just Google's implementation?
  - ahomescu1 13y ago
    There's a bitcode spec [1] and a stability doc [2]. 1 - https://developers.google.com/native-client/dev/reference/pnacl-bitcode-abi https://developers.google.com/native-client/dev/reference/pn... 2 - http://www.chromium.org/nativeclient/pnacl/stability-of-the-pnacl-bitcode-abi http://www.chromium.org/nativeclient/pnacl/stability-of-the-...
- azakai 13y ago
  The code is open source, but last I heard there isn't a spec for PNaCl/PPAPI.
  - eliben 13y ago
    The PNaCl ABI is defined here: https://developers.google.com/native-client/dev/reference/pnacl-bitcode-abi https://developers.google.com/native-client/dev/reference/pn... - and it's definitely a work in progress we'll be trying to improve. As for Pepper, it's also all documented here and below - https://developers.google.com/native-client/dev/pepperc/ https://developers.google.com/native-client/dev/pepperc/ Granted, this is documentation, not a standards-body spec.
    - azakai 13y ago
      Yes, certainly has had effort put into proper documentation. Do you know if there is also work being done to spec it formally?
      - eliben 13y ago
        We're definitely considering it.
- bzbarsky 13y ago
  For Pepper? There is not, in fact. There's some developer documentation, but nothing resembling an actual implementation spec.

by pvnick 13y ago

axelf 13y ago

How is this proprietary? Isnt there an open spec?

cpeterso 13y ago
Is there a PNaCl spec or just Google's implementation?
- ahomescu1 13y ago
  There's a bitcode spec [1] and a stability doc [2]. 1 - https://developers.google.com/native-client/dev/reference/pnacl-bitcode-abi https://developers.google.com/native-client/dev/reference/pn... 2 - http://www.chromium.org/nativeclient/pnacl/stability-of-the-pnacl-bitcode-abi http://www.chromium.org/nativeclient/pnacl/stability-of-the-...
azakai 13y ago
The code is open source, but last I heard there isn't a spec for PNaCl/PPAPI.
- eliben 13y ago
  The PNaCl ABI is defined here: https://developers.google.com/native-client/dev/reference/pnacl-bitcode-abi https://developers.google.com/native-client/dev/reference/pn... - and it's definitely a work in progress we'll be trying to improve. As for Pepper, it's also all documented here and below - https://developers.google.com/native-client/dev/pepperc/ https://developers.google.com/native-client/dev/pepperc/ Granted, this is documentation, not a standards-body spec.
  - azakai 13y ago
    Yes, certainly has had effort put into proper documentation. Do you know if there is also work being done to spec it formally?
    - eliben 13y ago
      We're definitely considering it.
bzbarsky 13y ago
For Pepper? There is not, in fact. There's some developer documentation, but nothing resembling an actual implementation spec.