5 ms·
I'm slightly disappointed by the target end date : 31 July 2019. WebAssembly seems like a huge deal to me and I was hoping things would progress quicker than t
by grondilu 9y ago
I'm slightly disappointed by the target end date : 31 July 2019. WebAssembly seems like a huge deal to me and I was hoping things would progress quicker than that :(
- TomMarius 9y agoLet's not mess it up just because we want it quickly, if we (they) do this correctly, it might be the final big progression, but if we do it too quickly, it might turn into the next JavaScript (problem-wise).
- alekratz 9y agoThis. They want to get it right, and iron out any kinks NOW so we aren't worried about "breaking compatibility" 20 years down the road.
- nickthemagicman 9y agoWhy can't we have versions that can be turned on and off? It seems like a no brainer to avoid javascript nightmare. Thinks will still need to be updated.
- twoodfin 9y agoTwo points: - Presumably there's a preference to be pessimistic on schedules so they don't have to go through the process of being re-chartered if things drag on unexpectedly. - By the time the standard is wrapped up, you'd expect the major browser vendors to have had fully production-ready implementations for a while, just waiting on any final tweaks. (Also, v1 is supposed to have achieved recommendation status by Q2 2018.)
- titzer 9y agoThat's the expiration date for the charter. The charter is now approved and can be renewed. It's already enabled by default FF and Chrome (since March 2017), and both pass the huge battery of standardized tests.
- detaro 9y agoA charter end date is not the date when their work is published. It's the date the working group ends and can not publish/proceed with additional standards.