4,015 karma · joined May 31, 2011
In fact I wouldn't be surprised if you could lose your financial advisor's license for suggesting everyone keep their life savings as cash - it's such bad financial advice.
If you keep your life savings as cash you are optimising for the 99th percentile of bad outcomes for the global economy, and losing out massively in every other likelihood.
>it could even be $0.00
It is unlikely that the value of the S&P500 will be zero in our lifetimes. If it is, your 50,000 US dollars won't be worth much.
What do you mean by "handled appropriately as savings"? Cash is riskier than stocks over the long term. Investing is the safe way to handle your life savings.
Cola from the fountain tastes more interesting, like the other flavours are more prominent over the raw acid and sugar flavours.
Anyway I prefer Pepsi :)
Written in Go/Rust is definitely a feature for something like this.
Well yeah. What if I spent all the time I spent on various types of consumption on deliberate practice. I'd be some kind of wizard by now.
There's nothing specially bad about these kinds of video in that respect.
If you create a file in Finder with a hangul name, by default ls in iTerm2 will display the name incorrectly, with the composite syllables expanded out into separate characters. There is an option in iTerm2 to 'normalise unicode' which corrects this issue if set to HFS or NFC (if I remember right). This mimics the behaviour of Terminal.app.
However, different interactive terminal apps seem to have different expectations of terminal behaviour for this form of unicode hangul. With the 'normalise' setting off, fzf will corrupt the display when showing hangul. But with it on, vim/neovim will corrupt the display when navigating lines with hangul text.
It seems there is no way to get consistent and user-friendly hangul handling in the terminal on macOS, but I'm not sure who's at fault (except Apple of course).
eg, I have worked with many so called 'developers'. They shipped lots of code, but most of it was solving the wrong problem, didn't fit any business requirement, added unnecessary complexity, had to be replaced almost immediately, etc. etc.
It reminds me of how sometimes you see a huge billboard hideously strong 10 foot wide JPEG compression artifacts. It was someone's job to make those, too.
And given all the confident comments in this thread claiming the author is full of shit and there's no difference, I think their frustration is justified? If you can't see the difference in the first images that's fine but you probably shouldn't be confidently claiming to know better than the author, let alone designing an image codec.
And if this is true it just proof of the merits of WFH. If everyone is 'slacking off' and productivity is basically unchanged, it just shows what a waste of everyone's lives working in the office was.
>On the auction settlement date, the maturing Treasury securities are exchanged for the newly issued Treasury securities.
In net, the debt is only paid back when the central bank is actively reducing its treasury holdings, by rolling over less than the total amount of maturing debt. That is basically the reverse process of 'printing money', it takes the money back out of the wider economy.
>Why do you think people buy them?
Certainly 'people' buy them because they intend to get paid back, yes, but the central bank doesn't have the same motives. It increases and decreases the amount of treasuries it holds in order to control the money supply. That's the whole purpose of it holding treasuries.
edit: here's some bedtime reading https://theconversation.com/how-the-federal-reserve-literall...