svgbobrus VS wasmer

I recently had to draw some diagrams for documenting something. After looking at various Markdown-friendly options I landed on svgbob[1]. I believe it's a superior solution to these kinds of graph drawing tools for Markdown for one specific reason: the code is still readable. When I go to look at a Markdown file I don't always open the output. I will commonly open up a README file in Vim or just cat it to the terminal. In this case diagrams like those in this post is next to useless. I'm not going to read through some complex drawing definitions and try to visualise the results. With svgbob (or Typograms[2] or any of the other similar options) you can still read the Markdown text document and see the diagrams which is great!

Of course this comes with a tradeoff, drawing the diagrams can be a bit of a pain. But I believe this can be solved by a good Markdown editor or editor plugin. Alternatively a spec like this could be converted into an svgbob-compatible diagram.

[1]https://ivanceras.github.io/svgbob-editor/

Online playground svgbob-editor is also updated to use the latest version of svgbob. It is however a painfully slow to edit the diagrams from there, so it's better if you draw the diagram somwhere else and paste it to there.

There’s Svgbob. Plus when it comes to more complex diagrams or graphs where creating the ASCII art by hand in can be quite finicky, there’s a number of tools (including drawing tools) to make creating ASCII art much easier.

https://ivanceras.github.io/svgbob-editor/

svgbob

Since the post contains ASCII art, let me recommend you svgbob :)

The app can now render Svgbob code blocks (https://ivanceras.github.io/svgbob-editor).

This is awesome. I'd love to have upstream support in Wasmer ( https://wasmer.io )

WebAssembly is extremely portable. WebAssembly runs on: all major web browsers, V8 runtimes like Node.js, and independent Wasm runtimes like Wasmtime, Lucet, and Wasmer.

Unfortunately cosmopolitan wouldn't work for dockerc. Cosmopolitan works as long as you only use it but container runtimes require additional features. Also containers contain arbitrary executables so not sure how that would work either...

As for WASM, this is already possible using container2wasm[0] and wasmer[1]'s ability to generate static binaries.

[0]: https://github.com/ktock/container2wasm

[1]: https://wasmer.io/

I could not find any guide how to add WASM container capability to Docker running on Colima. This guide provides a few Colima templates for exactly this, which adds WasmEdge, Wasmtime and Wasmer runtime types.

Just suggested as well Wasmer on Twitter! https://github.com/wasmerio/wasmer

Looking forward to seeing the results :)

The Biome team has been incredibly fast on solving the challenge and achieving 95% compatibility with Prettier [1]

Just as a note, as it was not mentioned in the article, Wasmer [2] also participated with a $2,500 bounty to compile Biome to WASIX [3], and it has been awesome to see how their team has been working to achieve this as well... hopefully we'll get Biome running in Wasmer soon!

Keep up the great work!!

[1] https://github.com/biomejs/biome/issues/720

[2] https://wasmer.io/

[3] https://wasix.org/

It's funny how WebAssembly can help overcome most of the issues mentioned on the blogpost (packaging, configuration, portability) if addressed properly.

That's the main reason Wasmer [1] was created :)

[1] https://wasmer.io

Thanks for the mention to Wasmer.

I'll put here a link in case is useful for future readers: https://wasmer.io/