Another important aspect is that, without an external library like `wabt`, I can't just open Notepad, write some inline WASM/WAT in HTML and preview it in a browser, in the same way that HTML+CSS+JS works. Having to obtain a full working toolchain is not very friendly for quick prototyping and demonstrative needs.
The same limitation exists with "non-web" assembly. It turns out that having languages that compile to assembly makes a lot of sense for almost every real-world use case than writing it by hand.
WebAssembly is a compiler target, not a human-authored language. There is exactly one audience of people for writing wat by hand: spec and tutorial authors and readers. Anyone actually developing an application they want to use will use a compiler to produce WebAssembly. Prove me wrong and write Roller Coaster Tycoon in raw wasm if you want, but having written and maintained wasm specs and toolchains for nearly a decade, I will never write any wat outside of a spec or tutorial.
There is exactly one case where I'd like to write "raw wat" (and for that matter "raw wasm bytecode"): I'd love to do something like the "bootstrappable builds" project for wasm, starting with a simple wat-to-bytecode parser/translator written in raw bytecode, then some tools wirtten in raw wat for bootstrapping into other languages. :)
If all the app need is to upload a photo of PCB, <input type="file"> is more than sufficient. It's been baseline years ago.
For download, it can download from a blob URI. This is not an uncommon practice.
If (not verified since I'm using Firefox) it claims that "Gerber files are composed of many individual files so that those two don't suffice" and the app does involve Gerber processing, it could have been solved by introducing a zip library.
"Gerbers" are indeed several individual files -- there's one for each layer of the PCB, such as front copper, front solder mask, front silkscreen, back copper, back solder mask, etc, etc.
A zip library is precisely how other webapps that load or output Gerbers handle it.
On my first encounter with a Unix machine (an SGI IRC) I had heard that system help was available with the "man" command, so I typed "man"; the resulting "apropro what?" made me laugh out loud, and the other people in the room looked at me like I was some kind of idiot.
> I could recompile it but compiling firefox is a pain in the ...
Would second this. Mach uses Python, and the dependencies they use are a pain whenever no pre-built wheels are available. Especially so when you see that an "optional" Mach dependency for build system telemetry is what busting the configuration (not build) stage...
Header-only libs can help avoiding the troubles and complexity of linker setup. This might be even more important on Windows, which this lib "explicitly support".
reply