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…
Half the time, I post because I'm slightly peeved. Today, it's because of censorship on Reddit. The following was a "Shower thought" post that got deleted: I've never seen a man complain about a lack of plus sized male models.This was removed by a moderator when it reached the front page of Showerthoughts, with 1104 upvotes. The post had a number of popular comments which were also deleted, apparently due to wrong-think. The following was one of them: We claim women in magazines are "unobtainable beauty standards". Nobody cares that men have airbrushed abs in the same magazine. Nobody cares about the young men who are doing steroids to obtain these standards. They don't consider the whimpy kid with a healthy weight who feels inadequate because he's not ripped with a stone jaw. (Not to mention a 8 inch wang.) Because in our culture, a weak female ego is expected, but a weak male ego is pathetic. (/u/Snoozetrain)Guess the reason moderators gave for …
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.