CubeSimRS VS hackernews-sauron

Been putting further work into my Rubik's Cube solver. Managed to get a basic solver working using some variation of IDA*. Planning to refactor the code and then start optimising to make things go fast.

Been working quite extensively on my Rubik's Cube simulator and solver. Currently working on optimising my data structures and then eventually to getting a proper solver working.

Completely new and picked up Rust about 10 days ago. Started by heading straight into a project of making a Rubik's Cube solver while following the Rust book along the side.

I did the same thing in a hackernews clone, except it is using sauron, instead of yew. I think yew is using trunk, which create and generate a files named with hashes, so it changed everytime the files are built. I use wasm-pack to build the wasm and the glue js file, which doesn't changed every build. So it is easy to just embed and serve them server side.

I can vouch for warp, the experience has been smooth so far, no crashes. The url route might be a bit not intuitive at first, but comes easier the more you use it. Here is a port of hackernews I wrote using all rust stack.

I'm the author of sauron web framework and it has the capability of progressive server-side rendering as demonstrated in one of the examples. There is also a demo app which is a clone of hackernews which is built to be resilient in the event of failure in either the javascript or the server. It is extensively used in svgbob, which has been adopted as plugin for other projects such as asciidoctor and krokio.

There is an example project which demonstrate its fullstack capability.