It will be less than %100, because of the unrealized losses on SVB's bond portfolio. Regardless of the amount, there will be delays in returning those funds as FDIC liquidates.
And also: at the time of Binance's offer to buy FTX, it makes sense only if Binance saw significant contagion risks to FTX's failure. But then they got a little closer and saw the huge hole in FTX's balance sheet and decided that they couldn't do that either. So it's really the worst outcome - they signal that FTX is important to their own business, but then can't do anything to save it. Does not seem to be good news for Binance.
Binance already knew that there was a hole there. They had just triggered the bank run by calling it out. The attempt to bail out FTX later was only for saving face and maybe also because they freaked out but couldn't stop it at that point.
And if they didn't know how large the hole was, they must have gotten a pretty good idea before signing the LOI. Even if it was rushed, surely that would be the first question they ask.
It seems clear from CZ's public announcement of a $2b FTT dump that their intention was to destroy FTX and Alameda. So my theory is that the LOI was a trap to put a nail in the coffin, destroying any remaining trust in FTX.
Before they were merely starting rumors; the phony acquisition attempt let them declare "we've seen the books and FTX is unsalvageable".
The other commenter said that it's a joy to read and that's certainly true. If you're interested in software folk tales and such, it's worth getting.
I still see it recommended as a practical book however and indeed the book bills itself as "the second book you need on C", the book that will cover topics that other C books don't explain or explain poorly. But it's much too outdated to serve that purpose. In practice it means chapters discussing differences between K&R C and ANSI C and deep-dives into details of SunOS and MS-DOS compilers.
Some of the material has become misleading because the C language has evolved. For example, there's a lot of discussion about pointers and arrays, as can be expected. But there's no mention of strict aliasing and pointer provenance (these rules existed in C89, but compilers at the time didn't exploit them yet for optimization). And of course no variable-length arrays (introduced in C99). So you're not going to learn what you need to know in today's world.
The book also has almost no discussion about safety. The Morris worm is mentioned, but just as a piece of historical trivia. Browsing it now, I don't even find any discussion about buffer overflows.
Exactly. It's always inner joins unless there is a reason not, and then there should be logic to deal with the null results from the outer table. It's not strange to always do left outer either, it just makes reasoning about the query easier (start with the driving set, the inner/outer join the others as left joins). Mixing right and left outer always confuses me, and full outer joins are difficult to optimize, so I usually do left outer joins with unions in the rare case that I need a full outer join.
Earnestly, yes let’s talk about unhealthy eating and heart disease! Let’s talk about the food system, food education, food availability, pricing, and governmental subsidies. Let’s talk about the socioeconomic factors behind unhealthy lifestyles.
Let’s talk about heart disease! Let’s talk about racial and sex disparities in heart disease. Let’s talk about class disparities in heart disease. Let’s talk about why these disparities exist.
Public health is super fascinating and very complicated. We should be talking about it more!
If nearly %100 of the nba is vaccinated, then it's more likely that the break thru cases will outnumber the cases on the un-vaccinated, even if the vaccine is very effective at preventing infection. The vaccine does not need to be %100 effective for it to make sense from a public policy perspective.
