News for hackers. Stuff that matters.
Re:Why Write Python in Visual Studio? by bargl on Monday August 03, 2015 @03:00PM (#9998901)
2013 was a pretty big jump (IMO) for Visual studio. It added some cool features that I use all the time.

Filtering in the solution explorer. Peeking definition. Code Lens Parallel watch. (Ultimate Only) Number of references listed above the function and tests associate with it.

2015 has some even cooler stuff. It shows memory and cpu usage as you debug any program (tests/console/etc). You can call linq from the watch window (not sure where I saw this buy a key feature that was missing). The built in diagnostics tools are better (I use resharper so I don't really need that).

I also really like some of the built in Code Review tools they have, which you don't need if you do pull requests in git.

Re:Why Write Python in Visual Studio? by bliti on Monday August 03, 2015 @03:05PM (#9998944)
I assume those features are strictly for the MS stack. Am I wrong? Do they work with Python? In terms of costs, what do you pay for it (including the OS)?
Re:Why Write Python in Visual Studio? by bargl on Monday August 03, 2015 @03:27PM (#9999133)
Argh hate to fess this up but I think some of those features might be locked into MS stack. Just tried on my 2013 version on python and peek wasn't working. Will try 2015 later to see, but I'm not hopeful.