#wintercg — Public Fediverse posts

Runtime compatibility across JavaScript runtimes
https://runtime-compat.unjs.io/. Shows API compatibility across different JavaScript runtimes. The data is retrieved from runtime-compat-data, based on MDN's format. #WinterCG

It would be great if #AppsScript would support more of the #WinterCG minimum API. Almost nothing is supported except for WebAssembly, which is a little more challenging to use without `TextEncoder` and `TextDecoder`.

https://justin.poehnelt.com/posts/apps-script-runtime-limitations-wintercg/

#v8 #javascript #GoogleWorkspace

WinterJS is a #JavaScript Service Workers server by the #Wasmer team that uses Firefox's #SpiderMonkey runtime to execute JavaScript.

It follows the #WinterCG spec to aim for maximum compatibility with other services such as #Cloudflare Workers, #Deno Deploy and #Vercel.

🔗 https://wasmer.io/posts/announcing-winterjs-service-workers

WinterJS: “most performant JavaScript Service Workers server thanks to Rust and SpiderMonkey”
@wasmer
https://wasmer.io/posts/announcing-winterjs-service-workers

#ECMAScript #JavaScript #WinterCG #ServiceWorkers

@deno_land Is this getting standardized through the #WinterCG? Couldn’t see it mentioned here: https://wintercg.org/work

/cc @jasnell @lcasdev

Advancing web runtime interoperability with WinterCG
https://openjsf.org/blog/2023/06/22/from-openjs-world-2023-advancing-web-runtime-interoperability-with-wintercg-ethan-arrowood-vercel/
#ECMAScript #JavaScript #WinterCG

@developit There is the #WinterCG now that can take this on though (right @jasnell?) – which is great – they can push the specifying of web API:s in standalone runtimes

(And I kind of hope that won’t be achieved by simply adding everything as default globals but rather at least allow for some opt-in behaviors)

https://wintercg.org/