Some things haven't changed since the 1970s. Programming is still done in text files; and though we have syntax highlighting and code completion, source code is still best displayed in monospace.
Other aspects of computing work best with monospace, also. The Unix shells; PowerShell; the Windows Command Prompt. Email is still sent with a copy in plaintext, which has to be wrapped on a monospace boundary. Not least, this persists because HTML email is excessively difficult to render securely, and there are user agents that still work better with plaintext.
In all of these situations, the problem presents itself that the originator has to anticipate how text will be rendered in advance. You cannot just send text and expect the recipient to flow it. You have to predict the effects of Tab characters correctly, and word wrap the text in advance, often not knowing the software that will be used for display. In terminal emulation, e.g. xterm via SSH, when the server sends the client a cha…
From one point of view, cashing out is foolish. The price has gone up, and will go further. From another perspective, holding so much in BTC was already insane.
In 2013, I swallowed my pride for not having invented Bitcoin, and invested a total of $60,000 in it. About $30,000 was into Butterfly Labs mining hardware. This turned out to be mostly a scam. Time after time, the company delayed delivery, while actually, they were using hardware prepaid by their customers to mine Bitcoin themselves. A year later, I was able to receive my order refunded. I'm not sure that would have happened if it wasn't for a friend.
With the other $30,000, I bought around 250 coins on MtGox, at around $120. For months after, I had a disturbing gut feeling about leaving them there. I rationalized that it's safer to trust the world's largest exchange than to store them myself. When MtGox came crashing, I salvaged around 30. For a year, I beat myself up for ignoring my sixth sense.
For the most part, I find that Visual Studio 2015 is awesome. However, it did ship with kinks that need to be worked out. Not least, it has crashed on me from time to time, while working on a large solution.
I recently experienced a problem where I couldn't open Visual C++ projects (.vcxproj) after I copied them to another location. When trying to open the projects, VS 2015 would give me nothing more than this "extremely useful" error:
That is some talent, right there. That must have taken a lot of work to get this right.
After trying various things, and having researched this without success for a few hours, I finally got the idea to try opening the projects in Visual Studio 2013, instead.
Behold: VS 2013 actually displayed a useful error, which informed me that my projects had Import dependencies that I forgot to move.
So, yeah. If VS 2015 helpfully tells you that "one or more errors occurred" try VS 2013.