See Netflix disables use of the Chrome developer console.

Ostensibly, protecting inexperienced users from the social engineering exploit known as "self-XSS". Self-XSS occurs when an attacker convinces an inexperienced to paste malicious code into the developer console. This is why Facebook also disables the developer console (though Facebook reportedly provides an opt-out). But the real reason is probably three words: digital restrictions management. It's similar to how Google Play Movies refused to play on rooted devices prior to mid-2012, and other apps have needed things like "RootCloak".

Fedora's fault. In Xubuntu, a Debian derivative, all I have to do is sudo apt-get install chromium-browser.

Is this the fault of the browser or of the sites you visit? Back when sites weren't as image- and script-heavy, like Better MF Website, a graphical browser could actually fit on a 16 MB machine. Nowadays sites are covered with carousels full of high-DPI photos, plus developers think they still need jQuery and all its bloat just to get the site out the door faster.

Browser developers distribute the debugger with all copies of the browser to keep sites from intentionally detecting a debugger's presence and stopping working if one is found. If everyone has a debugger, the site operator can't block people who want to tinker, learn, and make a site more usable without blocking everyone.

Apple is free to port Safari to Windows or X11/Linux, but it chooses not to. It used to port Safari to Windows but no longer does.

A lot of sites are laid out so inflexibly that zooming in causes a horizontal scroll bar.

The forthcoming Let's Encrypt project will allow "get[ting]/creat[ing] an ssl cert" without any "bothering" beyond an install command.

Is it really of so little value that you care not a whit whether the data you received is identical to the data that was sent? If so, extract an identical number of bytes from /dev/zero. If not, then you need to at least use signing, and HTTPS does this for you.

If you're a purist, which PC do you use that has a free BIOS and CPU microcode? Besides, there are other distributions of Chromium Browser without the proprietary parts.

In my own testing, I typically assume half screen 960x1080 (press Win+Right to use Snap) and occasionally test on a 10" laptop whose screen has about the same width. The narrower layout works well with tablets as well.

Competition also slowly convinced Microsoft to at least try to keep up with the HTML living standard rather than stagnating. Users of Windows 7 are eligible for Internet Explorer 11, which supports new web platform features reasonably well according to caniuse.com. Right now the biggest headache is Internet Explorer pre-10, such as the IE 8 used by Windows XP diehards.

But it might be financially sound to just ignore the market of users of IE on Windows XP. Here's my reasoning: Operating system holes render browser security meaningless. If Windows XP is no longer supported, Microsoft is no longer patching known vulnerabilities that allow a miscreant to install a keylogger or other backdoor. And if a machine has such malware, any payment credentials or other private information sent to or from that machine isn't secret. A criminal could compromise Windows XP on a customer's PC, copy the credit card number that a user keys in, and then make fraudulent charges to that account. If you don't let users of known insecure browsers make a purchase, you won't have to worry as much about chargebacks.

If you have failing sight, you could set your system DPI bigger.

If you're concerned about webmasters using the px unit, consider that CSS defines 1px not as a hardware pixel but as 1/2688 of the distance from the eye to the display. This means it'll respect DPI as much as anything else does.

But how would that fix the units in customers' heads? "If I turn on ten 100 watt appliances, I'm using a kilowatt. Easy so far. And if I leave them on for an hour, I'm billed for one kilowatt hour." Until you get customers to think about their energy use using kiloseconds instead of hours and megaseconds instead of weeks, you're not going to be able to avoid anthropic units entirely.

Then why for many years have shared web hosting providers acted so irresponsibly by selling hosting that allows the use of only such a shitty language? I've seen "PHP hosting $5/mo; Perl/Python hosting $10/mo" from some providers.

Yes. A lot of Kindle editions sold by Amazon use Kindle-specific digital restrictions management.

But won't the store-bought stuff already be on the network, uploaded by someone who got to the store faster than you?

Shouldn't the web server be submitting messages through TCP port 587 (SMTP message submission with authentication) out to a dedicated mail server?

In theory, it should be possible to adopt good coding practices that leave out all the bad parts of PHP, in much the same way that Douglas Crockford recommends for JavaScript in his book JavaScript: The Good Parts. If you think the PHP interpreter inherently has poor security despite good coding practices, have you tried notifying the operators of Wikipedia?