4 ms·

I agree that a senior should know this, but at the same time I've never run into a problem at work that required me to start using web workers because what I wa

I agree that a senior should know this, but at the same time I've never run into a problem at work that required me to start using web workers because what I was doing was so CPU intensive. Most professional Javascript development is pretty run of the mill.

rumanator 6y ago
> I agree that a senior should know this, but at the same time I've never run into a problem at work that required me to start using web workers because what I was doing was so CPU intensive. A few weeks ago I interviewed a front-end developer who said that in his current job he rolled into production some code that blocked the UI for nearly 1 minute, and that problem was only noticed in production because during testing they didn't used realistic data. He then said that his approach to solve the problem was to rewrite everything from scratch using a faster framework. Unloading the blocking tasks to web workers wasn't even in his universe of potential alternatives. Suffice to say, he was not hired. If you're applying for a front-end position and are oblivious to basic GUI principles, such as how not to block the UI, then you might not be lucky.