LOL, Spoken as someone who sees it as a simple badge swap. While 2016 is new you can't NEED it - It offers new features that you may want to use, but it also stops functionality that currently exists (deprecated & discontinued features - some real gotcha's moving 2008R2 to 2016.) You also trivialise (or rather don't mention at all) the organisational significance of the database. It this a production system running 24x7 @ 999999. Any DBA can update the "SERVER" in ~30min (with outages), this doesn't mean the database(s) will work on the other side, or that all the attached applications will be able to reconnect and use them. So much has been glossed over with the vision of a new toy to play with...

LOL, this guy's had problems with deleting a file - so he's (badly) put some tests in. pfl = program file - as my best guess I think what was intended was to locate a file, check if it was readonly, make a copy in a different location, then delete the original -- all pretty straight forward. However rather the checking for readonly he toggles it, in his local storage (not on the file) - and he may toggle it, once or twice - so you can never know what state the file was. In the end Delete file - ignore any failures (including a file that doesn't exist). A perfect implementation of try {stuff} catch {nothing} finally {pretend it worked}

Remember it's not just a single layout... There are variants for single handed use (right or left handed) Use mouse & keyboard without dropping your mouse...

It matters big time... Anyone using Source Control needs to consider the implications, in particular when working on multi-developer projects. Source Control (most of them) only store the delta (changes) of the code. Now this setting is a personal preference, so each IDE can set not only how many spaces = 1 tab, but also if it should convert one to the other. (how it handles quoted strings is another story) As devs checkout code, don't like the formatting, change it, and check it back in. You end up with source deltas that contain nothing but tab to space and space to tab conversions - and possibly 1 or 2 real code changes. (and it all has to be stored somewhere) This becomes more problematical when it comes to merging code branches. Tab/Space conversions often upset the offsets used in deltas which results in a merge requiring manual intervention to correct conflicts. I don't care which one you use individually, but if you're working on a group project EVERYONE needs to be using the same settings.