3 ms·

Is this the same case as with HTML5 that W3C takes what WHATWG creates, stamps their "approval" and then it's the W3C that "brings new language to the Web"? Co

by Boulth 7y ago

Is this the same case as with HTML5 that W3C takes what WHATWG creates, stamps their "approval" and then it's the W3C that "brings new language to the Web"? Could someone in the know shed some light in this matter?

dmitriid 7y ago
It looks like w3c is just late with the announcement. From https://webassembly.org https://webassembly.org: --- quote --- Developer reference documentation for Wasm can be found on MDN's WebAssembly pages. The open standards for WebAssembly are developed in a W3C Community Group (that includes representatives from all major browsers) as well as a W3C Working Group. --- end quote ---
- nerdponx 7y ago
  Off-topic, but I wish Markdown had a proper "multi line" block quote syntax like this. The current standard of ">" is open to too much interpretation around paragraph breaks. Similar to how fenced code blocks with ``` are a major improvement over prefixing the line with 4 spaces.
  - vanderZwan 7y ago
    The difference between code blocks and block quotes is that you can nest the latter. On the one hand that makes multi-line syntax even more useful. On the other it would make reading block quotes hard to follow when reading MD in plain text (then again, who still does that these days?)
  - thaumasiotes 7y ago
    In Markdown you can generally produce a single block quote with paragraph breaks by including quoted empty lines: > Paragraph 1 > > Paragraph 2 Whereas you'd get two sequential quote blocks by using an unquoted empty line: > Quote 1 > Quote 2
    - infogulch 7y ago
      That doesn't work here > because if you have multiple lines not separated by an empty line, > > even with a "quoted" extra line, it's not formatted on hn as such, and everything collapses into a single line.
      - steveklabnik 7y ago
        Hacker News comments are not Markdown. https://news.ycombinator.com/formatdoc https://news.ycombinator.com/formatdoc
      - thaumasiotes 7y ago
        Well, yeah, why would it? You can't get quote blocks here either.
domenicd 7y ago
Not really; the WebAssembly work is all done within the W3C. Specifically, it is done within the WebAssembly Community Group (open to all), then shuffled through the WebAssembly Working Group (open to paying member companies only) for advancement through the official W3C processes. This is a reasonable process hack for getting openness within the W3C structure. That said, the "Recommendation" stamp of approval is indeed being overblown in this article. What it practically means is: - (Pro) now all of the member companies of the WebAssembly working group (https://www.w3.org/2000/09/dbwg/details?group=101196&order=org&public=1 https://www.w3.org/2000/09/dbwg/details?group=101196&order=o...) have pledged not to use their patents to sue anyone who implements the WebAssembly specification. - (Con) now there is a static "dead standard" at some https://w3.org/TR/ https://w3.org/TR/ URL which people will treat as more official than the actual living drafts at https://webassembly.github.io/spec/ https://webassembly.github.io/spec/, despite the living drafts being actually up to date with implementations and the dead standard existing only for patent purposes.
mirekrusin 7y ago
I think they wait for 3 independent implementations to be available before making it a standard.

by Boulth 7y ago

dmitriid 7y ago

It looks like w3c is just late with the announcement. From https://webassembly.org https://webassembly.org: --- quote --- Developer reference documentation for Wasm can be found on MDN's WebAssembly pages. The open standards for WebAssembly are developed in a W3C Community Group (that includes representatives from all major browsers) as well as a W3C Working Group. --- end quote ---

nerdponx 7y ago
Off-topic, but I wish Markdown had a proper "multi line" block quote syntax like this. The current standard of ">" is open to too much interpretation around paragraph breaks. Similar to how fenced code blocks with ``` are a major improvement over prefixing the line with 4 spaces.
- vanderZwan 7y ago
  The difference between code blocks and block quotes is that you can nest the latter. On the one hand that makes multi-line syntax even more useful. On the other it would make reading block quotes hard to follow when reading MD in plain text (then again, who still does that these days?)
- thaumasiotes 7y ago
  In Markdown you can generally produce a single block quote with paragraph breaks by including quoted empty lines: > Paragraph 1 > > Paragraph 2 Whereas you'd get two sequential quote blocks by using an unquoted empty line: > Quote 1 > Quote 2
  - infogulch 7y ago
    That doesn't work here > because if you have multiple lines not separated by an empty line, > > even with a "quoted" extra line, it's not formatted on hn as such, and everything collapses into a single line.
    - steveklabnik 7y ago
      Hacker News comments are not Markdown. https://news.ycombinator.com/formatdoc https://news.ycombinator.com/formatdoc
    - thaumasiotes 7y ago
      Well, yeah, why would it? You can't get quote blocks here either.

domenicd 7y ago

Not really; the WebAssembly work is all done within the W3C. Specifically, it is done within the WebAssembly Community Group (open to all), then shuffled through the WebAssembly Working Group (open to paying member companies only) for advancement through the official W3C processes. This is a reasonable process hack for getting openness within the W3C structure. That said, the "Recommendation" stamp of approval is indeed being overblown in this article. What it practically means is: - (Pro) now all of the member companies of the WebAssembly working group (https://www.w3.org/2000/09/dbwg/details?group=101196&order=org&public=1 https://www.w3.org/2000/09/dbwg/details?group=101196&order=o...) have pledged not to use their patents to sue anyone who implements the WebAssembly specification. - (Con) now there is a static "dead standard" at some https://w3.org/TR/ https://w3.org/TR/ URL which people will treat as more official than the actual living drafts at https://webassembly.github.io/spec/ https://webassembly.github.io/spec/, despite the living drafts being actually up to date with implementations and the dead standard existing only for patent purposes.

mirekrusin 7y ago

I think they wait for 3 independent implementations to be available before making it a standard.