Oh, and in Hebrew, while it's not acknowledged by the speakers themselves, there's also two different ways to pronounce "L" ("lamed"), while English speakers only utilize one of the two ways. So, they manage to say "lomed" (לומד, studies) more or less correctly, but "lo" (לא, no) sounds funny to a native speaker, because the "L" is supposed to be "soft".
In many Slavic languages there's a concept of "soft" and "hard" consonants. In Russian and Ukrainian, for example, whether the consonant is of either kind is determined by either the vowel that follows it or a special other letter, or, in case of Ukrainian, an apostrophe. In Polish, there's a diacritic sign for the same purpose, which is for some reason reversed for L.
Anyways. The example that is very tricky to get right for an English speaker in Russian is:
Sigh. Web. Not Internet. Why is this distinction so hard to make on a WEB site dedicated to technology?
The reason I keep repeating this whenever I see this is because I've seen idiotic mislabeling and mischaracterization materialize as idiotic legislature or idiotic activism based on the former. Someone invented the term "AI datacenter", and now there's a swiping movement of idiots fighting... datacenters. Same as with 5G before it.
Please. Please. Don't blame the Internet for something it has absolutely nothing to do with. Your misattributed criticism is going to be amplified by thousands of automatic and semi-automatic morons and, who knows, maybe people will start cutting cables or attack ISP crew as a result.
The same thing would happen on any platform. Social media diverged from the web a while ago - accessing it through web is like accessing Usenet through Google Groups. Its native environment is the corresponding non-web phone apps.
Science funding was different back then. It was a rich men hobby, something done for amusement or to impress other rich men.
Today, science funding comes out of the tax collected from everyone. The taxpayers want an explanation for how their money is spent. It could be, of course, vanity, just like it was before (taxpayer money is spent on sporting events, for example because people root for the athletes who represent them)... but, maybe there's a better way?
> Science funding was different back then. It was a rich men hobby, something done for amusement or to impress other rich men.
This is not the full story, but fits today's cartoon history caricature. In reality, there were also salaried employees who were teaching or working on developing practical applications, there were church fundings, the universities like Göttingen etc. Not all were particularly rich, Euler came from a modest background etc.
Erm... not really. Well, since you mentioned Euler: most of his funding came from the St. Petersburg Academy, which, in turn, was bankrolled by the Russian Czar (Catherine the Great, in this instance). The crown had absolutely no need to report back to its subjects on how and why it spends its money. The primary reason academies like that existed was that his or her highness wanted to impress their royal cousins with how intellectual they were and how much money they could spend on the matters they believed themselves to be responsible for.
That's why if you look back at scientific publications or organizations, a lot of them have a "royal" in their name "the royal society of this", "the royal college of that". This is because of their sponsors.
Since we are talking about Russia here, basically, until Alexander II (second half of 18 hundreds), there weren't any government institutions that could, in principle, manage the tax collected from the royal subjects and had to report and justify their activity. Until then, by and large, all the tax collected belonged to the crown and the crown was free to do with it however their heart desired. The initial ministry of education created by Alexander I (early 18 hundreds) was the first step towards transparency, but it wasn't much.
If you are interested in the reasons: both the liberation of the peasants and the defeat in the Crimean campaign created a large hole in the crown's finances. If, until then, the crown disbursed some undisclosed amount to the minister, who would use the money however he wished (mostly stole), the changes in the 1860s made it harder to steal (the minister had to report the expenditures). One could say that at this point, the current approach to financing the education began. A lot of things, however, were still subsidized directly by the crown or various elites, rather than in centralized government-sanctioned way. Another large reform, that made the system more transparent and rule-based followed in 1904, but since the Communists completely reorganized the government in 1917, it's hard to tell what the results might have been. It's only really since 1917 that education and science became exclusively financed by the tax and not through private donors.
Some complexity levels not mentioned in the article:
* Consistency groups. The article kinda almost gets there, but stops right before it realizes there's a problem. If you have multiple programs accessing the storage, s.a. a database (that you are snapshotting) and the application using the database, then you are risking an inconsistent snapshot when the database state you wrote is ahead or behind the application state. You need a mechanism to freeze all I/O beside the snapshot in order to ensure that the snapshot data is useful.
* ACLs. And similar external mapping to the storage being used, eg. what if the users come from an LDAP server? Similar problem with symlinks coming from/going to ouitside the snapshot.
* Sparse file support. Let's say you have a few VM images in your snapshot: if your tool doesn't support sparse files, it will likely greatly inflate the image sizes.
Bottom line, either use the product's own snapshot functionality (ZFS has those), or switch to the product that does.
Thanks for the input. These things never crossed my mind, even the first one which in hindsight should have been obvious to me. I will update the article to include these.
Programs like filesystems typically have their own schedulers that aggregate writes, it would be an extreme performance hit if they wrote each checksum individually, as a separate I/O operation. They are certainly bundled with some other data that needs to be written.
And if you are concerned about the compute rather than storage, then writing to a block device is still slow enough so that computing a checksum isn't important performance-wise.
Failures in storage software are very rare. Which makes it very hard to test... (you need to run it a lot, for a very long time if you hope to find errors by chance).
Also, some failure modes are worse than others. The failures known as DI (data integrity) are the worst. Even though they aren't expected to happen to everyone at a certain frequency (because, again, mature storage software is comparatively very reliable), even a single DI error that happened to any user sets up a major alarm.
In the storage industry, the running joke is that after first DI in your product you lose funding, after the second DI you loose the product.
And it did happen to Btrfs quite a bit... I've seen it with my own eyes when a system didn't come back after power failure. (But I'm in the business of testing software storage products, so, it's less surprising that it happened to me).
So... it's perfectly plausible that you have never seen Btrfs fail, and it's been more error prone than eg. EXT4. The error rate is low enough so that if you don't actively try to cause the error you will never experience one. But, over a large group of diverse use patterns, the rate is still worse than expected.
I disagree with the (2). The laws of war are and have been evolving, and there's plenty of evidence in recorded history. The first records we have come from Ancient Babylon and they have been modified and amended multiple times since. Another aspect of this development is the existence of international arbitrage with laws that also keep evolving, something that minimizes the need to go to war.
And there's more: the relationship between the state and its army changed a lot. The role, the rights and the duties of individual soldiers changed a lot. Just to give you some examples: the Lieber Code is the one created during the US Civil War -- it's perhaps the first to mention the concept of unlawful orders, exonerating the soldiers who wouldn't follow such orders. Traditionally, St. Maximilianus is described as the first conscientious objector to draft, a concept that, too, went through multiple iterations... And, really, we didn't even scratch the surface mentioning these. Military history is probably the most eventful and rich sub-field of history.
In Israel, we used to have post-office issued debit cards. You buy the card at the counter, with cash, and then it could be used for online payments, until you exhaust your credit. This is not entirely different from a bank, of course, but it allowed users to separate their purchases history from their income history.
Post office is also used for things like utility payments. You can pay them online, or write down the invoice id, the recipient, and pay with cash at the post office. I'm not sure how it works from the recipient perspective: i.e. how would you register your business with the post office, but, the existence of some such payments implies it should be possible.
NB. Also, technically, these services while physically provided in the post office are sometimes referred to as being provide by "postal bank". I'm not sure why it's called a bank though, since it doesn't provide key banking services s.a. loans or check-in accounts... Maybe it's just a "historic" name.
I doubt Iranians needed sanctions as an excuse to install their own CAs and require their citizens to use them. Many authoritarian regimes require their citizens to use domestically produced networking software that is different degrees of compromised.
reply