4 ms·
It is so subpar compared to native, both in terms of time needed to reach the result (6 weeks 4 engineers) and fps (30 fps, no low pass filter, lots of noise an
by batmansmk 9y ago
It is so subpar compared to native, both in terms of time needed to reach the result (6 weeks 4 engineers) and fps (30 fps, no low pass filter, lots of noise and drop in the result...) that it confirms me that wasm is not ready for primetime. Overall, the web techonologies are loosing ground.
I wouldn't build any company around this technology.
- sp332 9y agoBut it runs on every platform with a webasm-enabled browser without installing or recompiling anything. It seems like a lot more potential users for a lot less work than targeting every hardware platform.
- markdog12 9y agoI wonder how much of the perf/feature diff is due to lack of simd or threads? I don't even know if OpenCV uses either (I'd be surprised if they didn't), but both features are coming to WebAssembly.
- pletnes 9y agoRegular python/C++ API is threaded (to some extent). Parts of the C++ API is GPU enabled. Simd - pretty sure, the library originated at Intel, after all.
- callahad 9y agoI wouldn't be so harsh; this was a self-directed learning project as part of a 12-week educational course. And they totally managed to get it working, which is no small feat given that WebAssembly only hit v1 a few months prior, and the tooling is still rather rough.
- Houshalter 9y agoWasm is very new, give it time. It will eventually get support for SIMD and maybe multi threading and GPU compute. It's amazing you can get results this good without all that though. Anyway you are comparing apples and oranges. The alternative to wasm isn't native, it's javascript. And this is leaps and bounds better than js. Wasm is the new lowest common denominator language. Every platform supports it, it "just works" from the browser without requiring the user to do anything, and it doesn't require installation of any untrusted software. You can't say that for anything else.