Scottopherson

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.

Apparently is has a screensaver if you don't interact with the page after a certain amount of time.

Do you really go hiking with a ‘very loud’ Wonderboom speaker?

Oculus Rift 2, most likely. It was the newest hardware before Quest 2 and it has no physical hardware for eye adjustments.

> web devs are among the least educated, least sophisticated, most entitled and most whiny bunch there is

Of course, you're not spitting out generic flamebait with no backing evidence. That would be very low effort.

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.

Every action doesn’t need its own physical control. Knobs and buttons can be multipurpose. My mazda3 has touchscreen but it’s disabled because I can navigate and control everything with a single “command” knob.

"Many farmers in North Dakota can't prevent drillers from drilling — even if they'd like to. Decades ago, the rights to the minerals below those farms were separated from the rights to the land itself — which is why today, energy companies can move in, create drilling pads where they please, move in trucks and workers, without the farmers' consent."

Am I reading this right? A company can just plop drilling operations on a farmer's land?

I don't have the ability to downvote. Is it possible to undo an upvote? I sometimes upvote a comment by accident when viewing HN on mobile.

Will your trivial custom payment system come with counter-intuitive modal popups? Unclear subscription/unsubscription terms? Inaccessible or hostile refund or return policies?

I don't want to prematurely insinuate that you or other's solutions would all have such characteristics but as a consumer I don't care how developers get paid and I enjoy the benefits of Apple's integrated UX around iOS payments and subscriptions.

But I am also a developer and enjoy benefits of open-ness and choice in my work as well so I struggle with my opinions on this issue.