Oh man that is something I've been wanting as well.
366 karma · joined July 21, 2016
Oh man that is something I've been wanting as well.
When you do an htmx navigation to a new page, a discarded tab will "restore" only the last htmx fragment loaded, not the entire html page with style tags. Fix is to use unique url on push that isn't in local cache which forces a server reload on tab wake from discard.
For example say you have some data like (eg. string "abc123") in host memory and then pass into module A which then reads/operates the data, and then returns some other data to the host. The host then calls into module B passing the original host data and data returned from call to module A. Can that original host data be shared efficiently and managed by WASM GC between modules?
1. It's too damn hard to get data into and out of wasm modules. The component model is addressing this but it's sprawled out into literally rebuilding "worlds" and turning wasm modules into sort of lightweight virtual machines. I wish there was just more of a focus on getting data into and out of modules first.
2. Lack of GC which has made languages like js/python/jvm/c# unfeasible. WASM GC is just now available and hopefully ship compilers can target and build wasm modules that aren't so large in not too distant future.
Once we are past these 2 items, wasm can run free and really should become the final unit of deployment.
edit: I also suspect that like the jvm which started as a client tech, wasm will find more use on the server side, than on the client side in info/business type software.
I actually tracked down the original which has charts of how much was found, and is what should have been linked to in this post. https://www.consumerreports.org/health/food-contaminants/the...
Frankly it's frightening to consider the implications.
My use case would be a wasm based validation lib that could be used in the browser, in edge proxies like cloudflare workers, and in a variety of backends(py/node/.net/java). This approach would negate the need to package a wasm engine like wasmtime.
Of course the "component model" or some agreed upon structure of data shared among modules and the mappings to each language is the missing piece.
Precisely why credit cards are a hidden parasite on overall economic activity. They incentivize customers to use to get rewards and then take a ~4% cut of the payment from the merchant. So that's why merchants charge you extra fee they need to make up that 4% cost somewhere and it's either fees or raising prices even though you might not realize it.
Do you have any plans for a standard library? Build one specific for the language, or will perhaps try use or create/collaborate on a cross language standard library based on wasm component model? Is this even possible or good idea?
May I ask the toolchain you're using to build Moonbit?
> "A fully self-contained natively compiled C# Hello World, including GC and everything can be as small as ~440 kB."
.net classic framework is windows deprecated legacy, and really no new apps should be built on it.