|
|
|
|
|
by vosper
2293 days ago
|
|
> it was causing (inadvertently) massive slowdowns periodically due to a naive approach to scanning a system for installed applications. > Turns out, it's running a node.js server and the whole UI is rendered in HTML/CSS/JS, but because of that it was so non-performant that the UI would effectively not render at all if it couldn't slam your CPU. So was it the naive approach to system scanning, or the web-based UI that was the problem? Because there are some performant desktop applications using web rendering, like VS Code. Though I'm not sure how VSCode would behave if limited to 10% of CPU, because that's kind of a weird scenario. |
|