The CLI does use StdRng which is a CryptoRng, so no real problems.
However, they seem to be using `XorShiftRng` in their tests, which is no cryptographically secure, so they can't use `CryptoRng` over `Rng` in their API without resorting to compile-time magic. I think they should just use `StdRng`, which is cryptographically secure and quite fast.
That logo is certainly lacking more marbling.
Also irrelevant I know.
From their blog and using Google translate:
It is believed that wagyu cows have that level of fat for a matter of survival. In Japan the winters are cold and the grasses are not especially rich in vitamin A. It is estimated that at some point in the evolution they achieved the ability to increase their own intramuscular fat production, which today is the characteristic of this race
I currently do consulting for a well-known company in the cryptocurrency space, and since I have done, I've noticed that Rust's adoption in this industry is far, far higher than anywhere else. I regularly get inquiries to do work in Rust there, but basically nowhere else.
Even if this is technically true (and I'm not really convinced that it is) it is not practically meaningful.
Do you have any links or an explanation that elaborates on this?
WebAssembly has also been on an upward trajectory in this space, and so there’s some synergy there too.
* Rust meets basic constraints (performance, reliability)
* A few early movers chose rust, and they likely share information and libraries, so it makes sense to just go in on it
Given that cryptocurrency is a fairly young space, having everyone leveraging the same tooling probably increases productivity. One day someone might say "We can get more productive if we leverage Language X, let's invest there", but until then everyone else is probably thinking "Oh, the libraries I need are in Rust, guess I'll use Rust".
2. “Wagyu is a lightweight”. i beg to differ.
not-much-ceremony-to-use (e.g. https://github.com/emilk/loguru)
small amount of code but huge number of dependencies (e.g. micromodal https://github.com/ghosh/Micromodal/blob/master/yarn.lock )
But the common denominator appears to mean "feature incomplete".
>Visual Studio Code is a lightweight but powerful source code editor ...
The existing name is weird and not fitting at all though, that's for sure.
one thing I find tricky about cryptocurrencies is that payment processors have snazzy interfaces for accepting crypto, but the similar interfaces don't seem to be available for open-source non-intermediary payment flows.
payment flows seem to be almost non-existent.
Its like "here just accept bitcoin" - when I really want to accept Monero - and there is almost no out of the box solution that rotates addresses for you, gives users a countdown and address solution, listens for transactions of the correct amount to that address to automatically update the payment site etc
And yes, the abscense of merchants seriously trying to accept crypto, and the abscence of people seriously trying to spend it does it make a self-fulfilling prophecy.
but fixing these other problems of lack of free library will go a long way to fixing the speculator conundrum