Tesseract.js VS binaryen

What do you have against tesseract.js?

Are you able to use a OCR library in the browser? Here is one I found

But keep in mind, PDFs can be fully or partially made of images, and if you want text out of those, you will need to OCR them. There's tesseract.js for that.

Tesseract.js

YOu could try using tesseract.js to OCR the images. Though might be a challenge to figure out the times/days of the classes.

I've never used it - but Tesseract.js looks interesting. Perhaps you can use it as a foundation on which to build something like the AWS tool (which seems to work by overlaying an SVG over the top of the image, then manipulates that SVG when user clicks on a results tag to get the word/phrase's highlight box to display)?

I tried researching a little on this topic, so from what I understand to achieve this feature, I would need a library that supports Optical character Recognition (OCR) such as Tesseract.js or Google ML Kit to do it. However, I'm not too sure if these libraries will be supported on React Native apps.

It's definitely one of the best for on-the-fly OCR, but I think a server-based implementation using Google's Vision API would be way better. Definitely not mine, the AI used here is way beyond my skill level - link: https://tesseract.projectnaptha.com/

The Binaryen wasm optimizer (mentioned in the article) is always open for contributions,

https://github.com/WebAssembly/binaryen

The end of the related work section cites both wasm-smith and the Binaryen fuzzer (https://github.com/WebAssembly/binaryen/wiki/Fuzzing) and says, "They both provide a fuzzer that turns a stream of bytes into a WebAssembly module in order to test implementations. Their fuzzers always generate semantically valid test cases, but lack the targeting and tuning that Xsmith provides."

I look forward to reading more about how they do the targeting and tuning.

Binaryen or the LLVM of wasm: https://github.com/WebAssembly/binaryen

Download Binaryen

Probably https://github.com/WebAssembly/binaryen/, there were various rust bindings to it.

The final phase of our compiler is code generation. This phase takes the AST and converts it to a set of executable instructions. In our case, WebAssembly. To accomplish this, we are going to use a popular WebAssembly compiler toolchain called binaryen.

In this guide, we will be using TypeScript and NodeJS. The concepts are highly portable, so feel free to use the environment you're most comfortable with. Our only major dependency, binaryen, has a simple C API. You are welcome to skip ahead to the next section if you're using a different language.

What are the size and performance benefits of processing the Wasm payload with wasm-opt?

I would recommend looking into binaryen as it has it's own IR and can perform optimizations over it. It's also simpler than LLVM and has the option to produce binaries with debug names.

You can also use binaryen to optimize your wasm output