I'm not sure how they're rendering in the browser. But if the TUI is rendered to DOM elements and not canvas/webgl, perhaps it could be useful to use a browser automation tool like Playwright to run test suites against the TUI. If your project involves CLIs and web apps interacting with one another, you could exercise them and assert their behavior within the same test framework.
Jeez that's a big paint brush you're slinging around.
That's the problem when non-front-end guys make decisions about tech sometimes, they choose stuff that seems easy to integrate without caring about things like accessibility, design scalability, client device capabilities, etc.
I became George after comedian Aziz Ansari had bit on one of his Netflix specials where he does math on how many times you can expect to see your parents.
Filtering a list is easy when all the data exists on the client and has no advanced filtering controls.
I'd love to slap an input box above a table and call it done but the product owners and designers that fill my backlog have other ideas.
I'd love to make sure this CSS visibility filtering worked well for screenreaders and other accessibility tools but that ticket was pushed down the backlog in favor of replacing native inputs with custom inputs that better match our branding guidelines.
I'd love to make sure these new custom inputs we cranked out last sprint work well for screenreaders and mobile devices, but we had another marketing lead join the company and now the branding guidelines are changing again.
I'd love to just focus on some HTML and CSS, maybe improve some of the touch support for mobile users, but now the release engineering team wants to have a meeting about micro-frontends?
I'd love to get past the existential crisis I had during that micro-frontends meeting and start working on the UI again, but first I have to debug all these failing Docker containers that's required to run our backend.
Really not sure where I'm going with this comment I'm going to stop now.
I recently learned that moving my mouse was causing the coil whine sound coming from my Win10 gaming PC. Turning down the polling rate on my mouse was the only fix that worked.
I started getting coil whine yesterday, after adjusting my fan curves. Not really sure why, but with the fans off the whine was far louder than keeping them on a low-speed minimum. It’s not fan noise blocking out the coil whine, because I still can’t hear the fans (they’re Noctua’s). I don’t know if it’s due to thermals, something to do with the power load, or what.
I’ll have to look at the polling rate thing, too - thanks for the tip.
I've also been hearing coil whine sound coming from MacBook's Caldigit dock when using a wired gaming mouse (only in totally silent rooms).
I haven’t mentioned it in the article, but just like you said, lowering the polling rate fixes it too.
Same issue here on a MSI laptop, the weirdest thing is that the coil whine is louder when opening certain applications like the desktop client of Signal and HoneyView image viewer.
