I suppose the difficult part is figuring when you've crossed the fine line from "good enough for now" to "this is becoming a monstrosity, we need to hire developers and create our own software now"
Happy to see that there is corporate sponsorship for this. Gives me some hope that this will allow MDN to outlast any eventuality that might befall Mozilla.
I used wasm for a computer vision related feature we built at work. It allowed us to reuse a bunch of things from opencv without having to reimplement those things in JS.
Interesting. I'm curious what machine spec you're on. I'm running Ubuntu 20.04 on an dell laptop (XPS 7590 with an i9 processor, 32gb ram, discrete Nvidia graphics card).
I see my processor spin up to 90% utilization whenever I do a zoom call.
They have an API using which you get a json representation of your files. That is the same as sketch (whose file format is essentially zipped json files).
> Guess which ones often have problems joining zoom meetings
As a linux user, I'd like to say that I've seen that happen just as often with OSX users on my team. I think that's just Zoom's shitty app. But I do agree about peripheral hardware issues plaguing Linux. Bluetooth headphones are still such a hassle on Ubuntu 20.04.
Hit me up at [email protected] if you want to talk about Computer Vision, Graphics, Kubernetes or something in between.