@tabatkins@zkat__ I point out in my write up that it misses aspects of the core proposal. My goal isn't to replace the current pattern matching proposal but to work with it.
2/ More & more authors are speaking out against this lawsuit: @sgcarney NYT bestselling author of "What Doesn't Kill Us" writes: https://t.co/Yua15928k7
The global cybersecurity community is concerned about #QWACs which could "actively expose citizens to increased digital risk at a time when protection is more challenging – and essential – than ever."
Read more here: https://t.co/MNSEORNUz6 #SecurityRiskAhead
Ecma International recently approved the 2022 standard of ECMAScript. But there is something new in this edition that hasn't been part of prior editions, and this isn't a new programming feature. 🧵 https://t.co/fErUJnY8Bm
ECMAScript, from 2022 on, will be using a new alternative license. This new license is based on the W3C Document and Software license. So, what has changed, and why is this important?
As part of our work to ensure a free and open web, we've been working with @EcmaIntl and many partners to write a #JavaScript specification license inspired by the @w3c Document and Software License.
Fantastic work by @codehag and many others! 🎉🎉 https://t.co/LdxYINwRpA
If anyone is interested, and would like to know the process or what their project can gain from going through a standards process, I am happy to answer and put you in touch with the right people! I think this was a great day for the open web, and open tech in general.
...Standards work more broadly. Ecma is now a home where projects can license according to their needs. This is a more light weight process and it makes me hopeful for what we can do in the future.