Generally, because they're discriminatory. It's like how racial profiling in law enforcement can be a heuristic that can work. Though, in the case of blood donations, it seems that tests aren't accurate enough to be able to rely solely on them. Also, being discriminated against on being able to donate blood is not as big of a deal. Though in some places with public health systems, stuff like getting a surgery may somewhat depend on you and family/friends donating a certain amount of blood.
"Linux, the open-source language of the internet" comes from the linked akamai.com press release, not the blog post author. Their putting that as a section title to the quote may be their poking light fun at it.
> I keep trying to explain to people that private companies harvesting your data, while not good, is done solely for the purpose of trying to get you to voluntarily buy more toilet bowl cleaner.
A reminder that governments can buy from private companies. A company like Palantir can buy data from private companies then incorporate it into the software it sells to governments.
> Well, the brackets thing and the necessity to repeat name of every element twice,
As a document format, it's supposed to be hand-written by humans. If you have paragraphs between the opening tag and closing tag, it makes sense to let the reader know what they're seeing the closing of.
After deciding you do want to repeat the element name, the angle brackets make more sense. Otherwise, you can have a syntax like LaTeX's.
> The worst part about it is the tags vs attributes fights. They both do the same thing and the only difference is preference.
They're not the same thing. If you look at it as the extensible markup language for documents that it is, "tags" (i.e. inner content) would be visible and "attributes" would not. If your XML document was processed by an application to convert to another type of document (PDF, etc.), and it didn't recognize a particular tag, it would be sensible for attributes to disappear, but inner content ("tags") to remain.
It's only seems like a preference thing if you look at XML as a structured data format like JSON is.
> developers must become domain experts [my emphasis] in a rich and complex space that is essentially unrelated to the application itself.
XML is a markup language, but most people that used it just needed a standard structured data format. In comes JSON which is more easily compatible with the object systems of various languages and in particular is compatible with Javascript syntax, and XML loses most of the people that used it.
As a markup language though, it seems pretty good. It's just that the amount of people that actually need an extensible markup language is much smaller.
I do hate the strictness of it. The header
<?xml version="1.0" encoding="UTF-8"?>
should be unnecessary. For a markup language, an already-made plain-text document should already count as XML. The tags should be something you can just sprinkle as you'd like to add contextual metadata.
> Most men who call themselves feminists got there by agreeing with ideas. Agreement is the easy part. The hard part is the gap between a man's stated principles and his Tuesday afternoon
Given the title, I thought this was about work on one's personal or professional lives. Never expected it to be some kind of call to action to male feminists.
如果它们得到了同意，那就不是真正的僵尸网络了......
这与餐厅和酒店的开放式 WiFis 以及大多数 VPN 服务并无太大区别。