The bank was nearly fully capitalized with low risk investments. Everyone would have gotten their money back anyways, it would have just taken 5-10 years.
Imagine what would happen if startups could not access their capital? By the time funds were available for withdrawal, the businesses would be dead. The regulators then have to track every funder to every dollar to return money. It would take a decade for this to happen.
I didn't see catch this part, but having 10 notes over 4 octaves is not out of the question. If all of those notes are rhythmic, that could be a challenge. All of the fairly wide chords I saw could be played either with sustain or could be easily substituted with spread chords.
Pop pianists don't usually play what's exactly on the page.
Question. From my experience, GitHub uses the `github-amo` bot to fetch the data when the page is rendered. How did you prevent it from cacheing on GitHub's servers?
Some societies believe it is acceptable to judge people based on their appearance. Arguably, most people do it instinctively. It is just that in America it was deemed illegal. I know there's an epidemic of plastic surgery taking place in some Asian cultures - people getting cosmetic surgery so that they can be employable.
Right or wrong, that is how some societies are functioning.
It probably helps that Julia and Fortran are both column major.
When interfacing with C languages, that can be a big penalty (depending on the complexity of the algorithm).
It will probably take two generations of developers to make this happen, but well worth it. When I was studying atmospheric science I tried to understand OpenWRF (weather research forecasting) and the barrier was too high... And I had programming experience, imagine those with none!
An open source project is only as useful as it is accessible to it's average developer base.
Somewhere there is a programmer that tried to fix a bug in 10+ year old legacy code (mso98win32client.dll) who has learned the bugs of legacy are features of today.
I really hope they do not do this. In and of itself it is not a problem, Ruby code is perfectly readable when the style is consistent.
Software developers are often stubborn. The main result of this change will be a mess of code which follows a mix of all the styles. That removes one of the greatest beauties of the Python ecosystem, that there is a "right way" to do things.
This presumes that the truth is knowable and you could know it.
Mathematics tells you what is not possible, but it tells you nothing about what exists. Every other discipline is separated from truth by bias in observation. And there are no perfect observers.
So, pushing "truth" is really pushing a specific perception.
Ooh, I missed those. Support for C++17 is pretty major. Thanks. Perhaps my memory is fuzzy, I just remember the CUDA 9->10 switch having some significant (but not major) performance and feature changes.
Does anyone understand why such minor upgrades resulted in a major version bump? Is this some sort of stability check point? Or some other versioning convention?
Teach them about cyclomatic complexity and then review their work in these terms. It gives them something concrete to target rather than trying to accomplish some ethereal notion of "proper abstraction".
What a beautiful conclusion for him on such a beautiful project. This man clearly loves the art of programming... so much, that he would give up power, just to pursue it again.
Thanks for the wonderful blog posts (over the years) and products.