[Docs] Unified environments / how we make your stuff just work page

[rdela]

Following on from https://github.com/socketsupply/socket/issues/875, Autogenerate CLI docs:

Might also be good to have a Unified Environments / How we make your stuff just work™ page.

Maybe in FAQ format? From Discord…

Q: Some things in Socket’s description sound too good to be true, is it true that you smoothed out all the differences between the webviews?

A: It is true, though we’re always open to people’s wants / desires / ideas for better DX and improved productivity.

Q: So I can just build something and expect it to work the same in all OSes, like I do in the browser?

A: [@heapwolf:] We fix more substantial and difficult things that are potentially too difficult to fix in “user land”, like a unified fetch for example. There may be some differences that we’re unaware of, we haven’t done a formal chart of every feature, but critical stuff, yeah we’ve normalized. It would be great for us to get into the MDN charts like Deno and Nodejs.

A: [@jwerle:] fetch() (including Request, Response, and Headers), URL, geolocation, navigator.permissions, Notification, File API, FileSystem* and File Pickers. We also introduce URLPattern in all environments. Soon we’ll introduce default response headers so you can set navigation headers for loaded HTML pages which should give you the ability to have cross origin isolation globalThis.crossOriginIsolated. Which will give you options to introduce SharedArrayBuffer. We also normalize Worker environments and give you a nice ESM standard libary there too. Soon we’ll also have the cookie story sorted out too so Set-Cookie works because we give you a unique origin too, which is based on your unique application bundle identifier. Import maps work everywhere now so stuff like this works without a build setup, just pure ESM:

import database from './database.js'
import sss from 'shamirs-secret-sharing'
import Tonic from '@socketsupply/tonic'

Q: How do you plan to monetize it?

A: We have tools for deployment and observability coming soon. Socket Runtime will always be fully free.

@chicoxyzzy may have a plan for how to chart or show what was possible to smooth out between webviews.