your constitutional right to a trial. They make you agree to binding arbitration instead. (Section 10 of the EULA).

That one really burns me. It's pretty unAmerican to say "Give up a constitutional right or you can't use our product." (Was that there before?)

How can this be legal? There's got to be a way around that. I have no intentions of ever suing Microsoft, but this rubs me the wrong way. What's next, you have to give up your right to freedom of speech?

Um, no, the default is "Express Settings" which enables all that spyful telemetry by default. Most people are going to go with that. I turned it all off except for crash reporting.

Interesting, thanks!

I totally agree. Git is way too focused on the repository maintainer than the day to day developer that just wants to check in code and not deal with the esoterica of the source control system. Even with Sourcetree it's just weird.

I use it for C#/MVC/WebAPI(REST) business apps. No node.js or python at work, although I do play with it outside of my work tasks.

Yes, if you're still using VS2010 I bet you're running into some issues.

One thing you might try is to make a \Code or \Source directory and move your projects there, rather than in \My Docs\VS\Projects - that does add a lot of unnecessary characters to the path name.

Very glad I'm working for a company that doesn't sit on it's hands with Visual Studio. Already have VS2015 installed on my work machine and I'm cleared to use it as soon as I get one our proprietary add-ins rewritten as a VSPackage extension. (They just nuked the old-school Add-Ins support in VS2015.)

That's what you get for unleashing your half-baked Git solution on the world. I've used it every day for two years and it is just a horrid mess. How many times I've had to do a "reset --hard" because a branch just shits itself for no good reason.

And what if I want to bring up two separate branches side-by-side to do some copying? Can't fucking do it in Git.

Linus, bless you for Linux. But curse you for Git. Git is Shit.

Dafuq?

"At my current job, we use Visual Studio to write web services in C#. The experience has shocked me."

What is wrong with it, or more likely: what are you doing wrong?

"the 260-character limit of path & file names"

That's a filesystem limitation, not a VS issue. But what on earth are you doing that requires anything that long in a Web Service? Are we talking old SOAP web services or modern REST/Web API services?

Hmmm, I threw down $400 on a Nokia 830 (Windows 8.1) several months ago and don't regret my purchase. You can stick to your iPhone you stupid weenie.

Then a lot of people/companies are going to hightail it back to local data centers. It's just a matter of time. Surprised it hasn't happened yet.

For internet-only companies, the cloud makes a lot of sense, but for a more old-school company it's just too much of a risk that too many are taking.

Some companies will be forced out of business the first long term cloud stoppage occurs, or even worse the first long term internet outage. Their people cannot do any work at all, cause they shipped it all off to the cloud, then the business cannot function. They are really going to be kicking themselves once they realize that all the money they thought they saved by using the cloud will be the thing that puts them out of business.

The cloud is still basically a v1.0 product. Too new to base an entire company's operations on until a few massive security breaches or loss of services occur.

Just drove from Missouri Valley, IA to Denison, IA on Hwy 30 the other day. Other than a few stretches of cement roads, the rest is horrible old potholed blacktop. Fix that shit you lazy bastards.

I once saw a flying saucer on a parachute after taking some LDSD, so getting a kick out of this...

Yah, it's MBii...

Anybody that quotes the Heritage Foundation is easily deluded. Maybe you can quote Fox News while you're at it? Give me a break.

"countries could be barred from trying to control where their citizens' personal data is held or whether it's accessible from outside the country"

The businesses pushing for this are the same businesses that are going to throw a fit when this affects them.

The end game here is to phase out cursive entirely, then a couple generations down the road, nobody can read it, and thus the US Constitution (written in cursive) will be meaningless gibberish to the common man, and then "they" can tell them what it actually "says" with their own injected bias.

Next up, a cashless society...