sserver VS wizer

did not abandoned it since i am using for myself but didn't put any effort into marketing either other than mentioning it on hn few times https://github.com/newbeelearn/sserver . It's hHeadless server for hosting courses and associated blog/static content from private github repository.

I am working on creating a hosting server that can cater to landing page+blog+selling digital content with minimal maintenance overhead.

Beta version is ready here https://github.com/newbeelearn/sserver

I am looking for following

working on adding e-commerce functionality to my simple hosting server https://newbeelearn.github.io/sserver/

if you want to self host, give my product a try https://github.com/newbeelearn/sserver. It will auto-sync your static site from git repo.

I built something that will take care of the publish part but not the static site generation part here https://github.com/newbeelearn/sserver. Right now it only has one user i.e. me :-)

./sserver -token "$GITHUB_AUTH" -repo "https://github.com/newbeelearn/sserver.git?ref=gh-pages"

My plan is to add e-commerce functionality to it so that users can sell digital content i.e. books/videos/courses etc. through single config file in their github repository where the content is stored without needing to change their workflow.

If you would like any specific feature please let me know in the comments or create issue in the repository. Looking forward for your feedback.

> once by the wasm runtime to compile the rust-python wasm

I'm not sure what you mean by that. The runtime doesn't compile WASM, it simply executes it.

There are tools for dealing with interpreter runtime overhead this by pre-initalizing the environment like Wizer[0]. ComponentizeJS[1] uses it to pre-initialize the Spidermoney engine it packages to gain fast startup times (and you can then prune the initialization only code with wasm-opt). As techniques like ComponentizeJS are also being applied for a specific set of interpreted files, you can even prune parts of the interpreter that would never be used for that specific program. If you want to go even further you could record specific execution profiles and optimize further by those.

[0]: https://github.com/bytecodealliance/wizer

[1]: https://github.com/bytecodealliance/ComponentizeJS

Edge functions are typically run intermittently, with their runtime stopped to free up resources between runs. Therefore a big factor is startup and shutdown speed. Containers are pretty bad there. Deno is better, and WASM is unbeatable, especially with things like Wizer[0].

[0]https://github.com/bytecodealliance/wizer

I imagine startup cost could be amortized by something like wizer: https://github.com/bytecodealliance/wizer

There are security benefits to running each request in its own instance, as it helps prevent accidental leaking of state between requests. To avoid doing lots of expensive initializations, we have a tool called wizer which lets users run their program's initialization once, create a snapshot, and then use that snapshot to do fast startups that don't rerun the whole initialization each time.

See https://github.com/bytecodealliance/wizer for an implementation of this approach.

It should probably be named "Making JavaScript to startup fast on WebAssembly", since the runtime speed is not really improved by the approach they exposed.

Besides that I think Wizer [1] is both an elegant and a simple solution to speed up startup speed with Wasm.

[1] - https://github.com/bytecodealliance/wizer#using-wizer-as-a-l...

A similar project, for WebAssembly so with limited scope is this: https://github.com/bytecodealliance/wizer. And somehow similar but limited on LLVM IR a colleague worked on this for Cheerp (the compiler used here as backend): https://github.com/leaningtech/cheerp-meta/wiki/Cheerp-PreExecuter.