I am learning about web workers. The premise makes sense but I am curious about the performance bottlenecks that would crop up by a web worker spawning more workers.
What happens with this when you are on a low-spec PC with maybe two processor cores and you're spawning multiple threads? Is there a way to handle this? I assume there to be a cap on the number of workers you can spawn. Interesting stuff.
Vite, Supabase, and TailwindCSS
TL;DR of Neetcode:
He spent a ridiculous amount of time solving Leetcode problems on YouTube for free and ended up getting a job at Google.
I also paid $20 for Fireship's Supabase course, which I am excited about.
$129 on sale which ends today for lifetime access, $199 when the sale is over. Or you could pay $99/yr. If I wasn't so broke while job searching I'd have given him $99/yr without hesitating. ↩︎
I pay so much for AlgoExpert yearly as they're big enough to separate their tracks into algorithms, frontend, and system design. I can't afford all three and just have the algorithms and frontend experts. Neetcode has the algorithms and system design courses I need, which reduces my need for AlgoExpert's courses. ↩︎