scenebuilder VS krustlet

SceneBuilder, good luck!

Can't argue with that, but to me it seems that things have substantially deteriorated since desktop GUIs fell out of fashion. Maybe that tells you more about my age than about the state of the art, but in the 90's one could "learn" GUI programming in about 30min in a RAD tool by throwing controls in containers and implementing callback functions in "direct style" for the event (Qt , swing, Java/ScalaFX, Gtk, Forms, delphi, …), or do all that in code instead, with objects representing components and inheritance/OOP doing wonders to encapsulate state, expose a type-safe discoverable API, and offer customizability through members override. Entire generations of corporate monks made visually and functionally convincing business apps with VBA in an afternoon for instance.

Yes it does[1] and it works on Desktop, mobile and web.

JavaFX has SceneBuilder[2] which also fit the description but for some reason, it never caught on. Gluon seems to have that work not only on desktop, but also on mobile.

[1] https://docs.flutter.dev/development/tools/devtools/overview

[2] https://gluonhq.com/products/scene-builder/

JavaFX (Desktop) -> Use Scene Builder standalone from Gluon. https://gluonhq.com/products/scene-builder/

Additionally you can learn JavaFX for desktop applications. JavaFX with Gluon Scene Builder (https://gluonhq.com/products/scene-builder/ ).

SceneBuilder

Just run it from source until you figure it out

Oh it’s certainly looking like that IMO.

You can run wasm in k8s: https://krustlet.dev/

Docker itself can run wasm: https://wasmlabs.dev/articles/docker-without-containers/

There are a few serverless runtimes based on wasm: https://wasmcloud.com/

A lot of those are powered by wasmtime or WasmEdge.

If you’re wanting to be able to just pull down a random app and run it as wasm, that’s inherently harder with wasm, because you have to recompile, and amazing compiling stuff is always harder than it should be. For example I compiled jq to wasm to other day, so you dont have to worry (as much) about the CVEs that was issued recently. https://github.com/rockwotj/jq-wasi

It can, kubevirt is a project for running VMs https://kubevirt.io/ and there have been more esoteric things like WASM (https://github.com/krustlet/krustlet).

Or you can run Krustlet instead of Kubelet. That makes it so you can only run WebAssembly on the cluster - so no Go, no Python, only Rust!

But the project seems to have died: https://github.com/krustlet/krustlet/graphs/contributors

There are some cloud providers that are starting to offer wasm support. Docker is currently working on wasm https://docs.docker.com/desktop/wasm/ There is also krustlet https://krustlet.dev/ which lets you run wasm in kubernetes

> If one writes Go or Rust, there are much better ways to run them than targeting WASM

wasm has its place, especially for contained workloads that can be wrapped in its strict capability boundaries (think, file-encoding jobs that shouldn't access anything else but said files: https://news.ycombinator.com/item?id=29112713).

> Containers are still the defacto standard.

wasmedge [0], atmo [1], krustlet [2], blueboat [3] and numerous other projects are turning up the heat [4]!

[0] https://github.com/WasmEdge/WasmEdge

[1] https://github.com/suborbital/atmo

[2] https://github.com/krustlet/krustlet

[3] https://github.com/losfair/blueboat

[4] https://news.ycombinator.com/item?id=30155295