I would check out the WebAssembly VM. There are many projects aiming to make it a lightweight embedded standard, and it's also in browsers. I think learning a bit about it might help swap between web/embedded.
WebAssembly also support WASI, a way to access OS system services. You can even access the GPU with WebGPU/wgpu at the same time.
For a GUI applications, Slint/egui/Rust offer cross platform GUI-toolkits that target embedded.
Cloudflare recently open-sourced workerd, a WASM/JS runtime that acts as a server/HTTP proxy. You can maybe use that monitor network requests, in combination with the above to manipulate OS/GPU/etc. at the same time.
Both Go and Rust compile to WebAssembly. They both support bindings for WebGPU and WASI. You can use whatever floats your boat and just compile to WebAssembly. The future is here my friend.
It's unlikely to change development significantly.
California NIMBYs still have enormous autonomy through CEQA. It enables any individual to contest developments for years, obligating developers enormous sums of money and time to study "environmental impacts".
Last winter, the law was expanded through a ruling in Berkeley. If a development adds a sizable number of people, it can be seen as an environmental impact and denied.
Development will remain costly, time consuming, and ultimately as unpredictable as the law allows. Wealthy and well connected developers might get by, but it won't be a Japan-like situation. For those wishing reform on an "environmental law" it will be a lot more politically costly. We'll likely get another Houston situation where "no zoning" doesn't imply what it should imply.
Perhaps not coincidentally, Berkeley's housing element was just rejected today (the deadline by which they needed it certified in order to avoid the Builder's Remedy). The provisions in this piece will kick in there tomorrow.
As for CEQA, here's what a local law firm has to say: "In particular, the intersection between Builder's Remedy and California Environmental Quality Act (CEQA) remains untested. Jurisdictions may try to use CEQA to regain discretionary authority over Builder's Remedy projects. Whether that tactic will prove effective remains to be seen, given that CEQA may not be used to do that which other statutes prohibit. Pub. Res. Code, § 21004; CEQA Guidelines § 15040(e)."
WebAssembly also support WASI, a way to access OS system services. You can even access the GPU with WebGPU/wgpu at the same time.
For a GUI applications, Slint/egui/Rust offer cross platform GUI-toolkits that target embedded.
Cloudflare recently open-sourced workerd, a WASM/JS runtime that acts as a server/HTTP proxy. You can maybe use that monitor network requests, in combination with the above to manipulate OS/GPU/etc. at the same time.
Both Go and Rust compile to WebAssembly. They both support bindings for WebGPU and WASI. You can use whatever floats your boat and just compile to WebAssembly. The future is here my friend.