Explore tweets tagged as #ECMAScript
🗓️Day : 40/75 ✅ Learnt about : 🔸CommonJs and EcmaScript modules #WebDevelopment #codewithharry #75DaysOfCode
1
0
12
ECMAScript excitement 😉 Congrats to @SpiderMonkeyJS developers Yoshi Cheng-Hao Huang, Jon Coppeard, Dan Minor on landing ES2023 "Symbols as WeakMap keys" in upstream SpiderMonkey. Heading for Firefox 146 🎉 This completes support across all major browsers 👍
Symbols as WeakMap keys, soon in all browsers! 🎉 A quite interesting low-level feature that could unlock various innovations It lets you hold weak refs to objects in a self-cleaning cache. Those refs can be sent at no cost to a Worker, for example
1
0
6
Is there something wrong with @Grok at the moment? It generates absolute garbage code compared to Gemini. Usually Grok has been better at these tasks where the algorithm is well known. This was an ecmascript web app that plays connect-4, but it didn't even manage to follow the
1
0
4
If you never heard of Error Cause, it's in EcmaScript now, and all browsers/runtimes support it well https://t.co/6wRmE6ja0B
Am I the only one excited? 🙌 Error Cause proposal just reached stage 4 ! ➡️ No more weird error logging / wrapping / contextual information loss Support: 💚 Firefox DevTools already logs nested stacktrace! 🧡 V8/Chrome/Node.js should follow
0
2
27
“Dateに代わる新たな日時表現・操作APIとしてECMAScript標準化を目指し、2017年にプロポーザルが投稿された Temporal。ついに仕様策定も大詰めとなり、Firefox 139での正式実装リリース” https://t.co/rnwglVSXiT
0
1
3
다시 생각해도 ES4가 뒤진 건 크나큰 웹 역사의 비극임 https://t.co/eSqDX5yk8o
0
0
2
・ECMAScript(ES)はJavaScriptの仕様 ・ESはEcmaインターナショナルのTC39委員会が定める ・ESは毎年6月に改定される ・ESの改定提案は公募され、ステージ4で採用される ・ブラウザはレンダリングエンジンとJSエンジンを持つ ・JSエンジンはESを実装する 『サバイバルTypeScript』より
0
0
2
otya128/es2: ECMAScript 2 implementation https://t.co/2ALdymYUXP web-bmlで採用しているJS-Interpreterでは限界があり、代わりにECMAScript 第2版の処理系を自作したもの(host object以外は実装済み)。 なお、ES2の実装は全てAIに頼ることなく書かれているとのこと デモ https://t.co/ZUtb6nZyaB
0
1
4
@cryptotusa True! Specifically we use a secure fragment of JavaScript called SES (Secure EcmaScript). We think its a solid choice as a smart contract language: * JS is the world's most popular programming language with the largest ecosystem * It runs natively in browsers enabling
0
1
6
@vanilagy @mazeincoding The thing missing from your explanation is what @ffmpeg is doing in comparison, if all the functionality is in WebCodecs anyway, is Mediabunny just calling the same APIs more efficiently, or is the comparison: -hw codec via mediabunny -ecmascript software codec via ffmpeg wasm
0
0
4