This is a hard business decision to make as it doesn't directly increase revenues and directly reduces productivity.
Might be smart in many instances to do cross training, and on the job perspective expanding, but at the end of the day: it's usually better to let the animous live...and the spice flow.
How well do investors understand the underlying network of computers required to maintain the public ledger and the trust and integrity of the digital currency, though?
Until nation-states fund and invest in the infrastructure, finding your confidence in cryptocurrency with little to no regulation is a massive risk.
Wild that as they grow and scale, sustainable or climate-sensitive power can't be sourced or relatively (directly) scaled.
It will be interesting to see over the next few decades if sustainable power sources (arguably Nuclear, especially under the recent Advance Act) won't just be a lagging situation.
Filtering (out) the meta categories would be nice (so you can look at just the meta categories or just the countries).
Something that I don't think is available at the source that would be a nice addition would be a per capita (looking at the population and using it as a basic sortable column for quick reference).
Great example of ground effect, between that and the amount of relative wind against its 'wings' providing a great angle of attack...the really impressive component to the entire situation is: how much thrust did that little guy start off with that it was able to maintain lift for so long?
They really do appear to be all in on avoiding memory leaks from C/CPP:
> Over the next few years we plan to continue replacing C or C++ software with memory safe alternatives in the Let’s Encrypt infrastructure: OpenSSL and its derivatives with Rustls, our DNS software with Hickory, Nginx with River, and sudo with sudo-rs. Memory safety is just part of the overall security equation, but it’s an important part and we’re glad to be able to make these improvements.
It seems like a really challenging endeavor, but I appreciate their desire to maintain uptime and a public service like they do.
There's a high bar to set for most organizations. Leveraging certificates is excellent if the supporting and engineering actors are all in accordance with how to manage and train the users and workforce how to use them (think root authorities, and revoking issued certificates from an authority).
I've seen a few attempts to leverage certificates, or GPG; and keys nearly always are an 'easier' process with less burden to teach (which smart(er) people at times hate to do).
Not always, as quite often the donation is on hand, but not necessarily used.
Also: better to save a life and either average down whatever PFA count they have, or bolster their blood volume so they can start producing their own lower PFA infested hemoglobin.
Lesser of evils, and kind of a win win: if everyone was blood letting for the safety and humanity of others.
Coming from a systems background (administrator, engineer, and architect for many years): this is horrendous, but insightful as to how things were back when it was written.
Coming up with a uniform, concise, and easily decipherable scheme is really the best for naming nodes on a network (be it at your home, or in a data center with 10s of thousands of machines (virtual and physical)).
GUID is a bit extreme, but leveraging DDNS, and having a plan is always the best (and not naming things after a finite index like: planets, cartoon characters, mythological objects, or models).
Might be smart in many instances to do cross training, and on the job perspective expanding, but at the end of the day: it's usually better to let the animous live...and the spice flow.