idbehold

Yes!

This fugazi economy is all too crazy.

For me it's #353841 on #ffffff which meets WCAG AAA standards for accessible text.

The amount of punctuation and terrible sentence structure make this nearly incomprehensible.

Manufacturers know people do this. The TV will attempt to connect to any open network (neighbors) and I'd be shocked if they haven't at least considered packaging them with 4G/5G antennas. You're gonna need a Faraday Cage.

If you try to render tables with millions of cells the browser does a really poor job and the performance is abysmal. The only solution when you need to render that many cells is to virtualize the table and only have the visible cells (plus some buffer) actually in the DOM at a time. That plus weird restrictions browsers put on certain table elements (looking at you thead) that prevent them from being "sticky" headers means that the developer is left with absolutely positioned divs as the only solution. Blame browser vendors for not providing a native way to present tabular data with more than a few hundred thousand rows without causing performance issues.

You also miss out on standardized HTTP caching mechanisms since those don't work with POST requests.

"Products" would have had no such ambiguity.

The term "range" (in the context of a "home") typically describes a multi-function cooking appliance that features a rangetop for heating pots and an oven directly beneath it. Why is this page about lightbulbs? The subtitle even has the word they should've used instead of "range": "products".

Counter point: yes they are.

Would be funny if individuals could do the same. "Sorry IRS, even though my income is $100k, the cost of living took all of that revenue."