Werrrrlllllll... It all depends on what yo umean by "type". In physics problems, I find taht quantities may be measured in "floats", but have the types "mass", "amperage", "distance per second per second" and the like.
In Go, I would probably model this as:
type mass float64
type speed float64
type acceleration float64
That way, they'd all have float64 as the "storage type", but it would be harder to accidentally pass an acceleration when I wanted a mass.
These days, my main use of dd is to get a specific amount of data from a file, where both "bs" and "count" are useful (no, "bs" does not only set the buffer, it also sets the chunk size for reads and writes, this is SOMETIMEs useful and/or necessary with tapes).
So, this is an approximation of a command pipeline I run several times per year, when I happen to need a secret of an approximate length:
dd if=/dev/urandom bs=6 count=1 | base64
Tune the "bs=6", depending on how long you want your (guaranteed typeable) secret to be. Every 3 bytes in the input will give you 4 characters in the output and keeping the input block size a multiple of 3 avoids having the output ending in "=".
It MAY be possible to replace this use of dd with other shell commands. But, since I needed to learn enough of dd to cope with tapes, I use that.
ON the international currency market, one traditional role of the US dollar is exactly "store value". You trade your currencies on the FX market during your day, and comes close to "close of your trading", you exchange all your positions for US dollars, to keep in store for your quiet period. Comes the following day, you trade out your dollars for other currencies. Then the cycle continues.
Does this mean that the US dollar is a terrible currency? No. If another currency meets the same stability criterion, it can (and probably is) used as a short-to-medium term value store.
I don't really see any crypto-currency work well, they're thinly traded, so there's a lot of inherent volatility in the pricing. It is also getting increasingly harder to exchange crypto-currencies for more traditional currencies.
> ON the international currency market, one traditional role of the US dollar is exactly "store value". You trade your currencies on the FX market during your day, and comes close to "close of your trading", you exchange all your positions for US dollars, to keep in store for your quiet period.
Come again? The international currency market doesn’t really close overnight, and the people who store value in USD are generally Americans or other people or entities who generally store value as USD.
And that latter part is the whole point. When you save up for retirement, or plan your business, or prepare a balance sheet, or plan for a college education, everything is denominated in dollars (or your local currency).
If you want to store money for any future use, you want an asset that has a somewhat predictable return relative to the dollar. If you are a drug dealer who collected $1M (in USD or its equivalent in Bitcoin, Monero, casino chips, whatever), you may well launder or mix it through something else, but your goal is to end up with approximately $1M for when you want to buy more wholesale drugs, pay employees, buy a fancy yacht, etc. Storing $1M as Monero is making a huge bet that it will still be worth $1M when it’s needed.
> ON the international currency market, one traditional role of the US dollar is exactly "store value".
I do know that 'store of value' is the term I used, but it is in reference to the people who hold Bitcoins in expectation of rising price, and the fact that they would claim it 'stores value' while being extremely volitile is indicative of their lack of understanding or their lack of honesty in representing their motives.
People who shelter their dollars overnight are most likely not expecting a return on it.
If you are selling A as A-prime, you can be a snake-oil salesman even if you are supremely skilled at A.
In Lars' case, he is from what I can see a supremely skilled instinctive archer. There are some historical documentation, from some regions ,documenting feats that Lars is capable of doing.
But, "feating" and "combat skills" are very different things (well, they are for sword disciplines, I will blithely assert the same is true in archery). Yes, both require skill. Yes, training one discipline can improve the other. but they're not the same. Just like how writing Haskell (or Lisp) can make you a better C programmer.
That'd depend on if they're the same entity as "The Billing Project LLC", that seems to own the "KILL BILL" mark for downloadable software. I hope they are the same.
Oh, boy, on the "never log expected failures as errors" front, I once worked with a database system that used opportunistic transactions. Basically, each modification to a row carried effectively the original value of that trow with the update and if it failed, the API call triggered an error saying that the transaction failed. So if you did a "SET column=(column+1) WHERE rowid=unique", the client could basically do an automatic retry.
But, it also logged each and every occurrence of this at "Error" severity, instead of at "Info" severity (it is, after all, expected to happen once in a while).
And of course, once our code switched over to using this, the first few times every team member had to deal with a production issue, the immediate reaction was "oh, no, the data store is unhealthy! look at this mass of error logs, I can see one every few minutes!". Thankfully, after the first team member (me, as it happens) spent half an hour reading the relevant parts of the design and implementation docs, we could frequently short-cut a lengthy investigation by "oh, you think $DB is bad because you are seeing transaction failures? no, that's expected, see $URL".
Then there's the delightful (no, I actually mean the opposite) errors that g++ emitted (back when I last wrote C++ and compiled using g++), where I basically could go "OK, there is an error that was detected at line L, in file F; and I think it may be a type error", so a recompile with clang, so I can actually understand what the error was, so I could fix it.
Likewise Digital, all VMS error codes are "SUB-S-NAME" (so a permissions error when dealing with a file woule be something like "%RMS-E-NOPERM" (I think that's "rotating mass storage" rather than "Richard M. Stallman"). I think that even harks back to various OSes on the PDP-11, but cannot say for sure.
Im always amused when I see the HN community get excited about something that the greybeards figured out 40 or 50 years ago. Turns out grandma knew what she was doing after all. If only there was a better way for the wisdom of sages to be transmitted to this generation without eyerolling over IBM and DEC.
My (very rough) estimate is that somewhere between 1% and 5% of those who enthuse about crypto-currencies are actually interested in the underlying tech. The rest being in it for one of "it's a safe way to do nefarious economy" and/or "it's easy money".
Me? I think the tech is intellectually interesting, but doesn't really scale to the point where it can provide a "world economy". If nothing else, with Proof-of-Work, you need 51% of ALL available computing resources dedicated to maintaining the chain, which is an incredible waste (if you don't have a majority of all available computing power, the chain is vulnerable). With Proof-of-Stake, you need a majority of the economic system dedicated to just maintaining the economic system.
So, intellectually interesting, but practically useless.
In Go, I would probably model this as:
That way, they'd all have float64 as the "storage type", but it would be harder to accidentally pass an acceleration when I wanted a mass.