Visual Studio and Team Foundation Server will have Git support
111–120 of 220 posts
Re: Visual Studio and Team Foundation Server will have Git support
#112Earlier quoted context omitted.
Some code like encryption algorithms cannot leave the United States by law (if developed by a US company/Citizen). Another example might be Credit Card Processing software, you don't want a lot of people knowing how you generate your encryption keys.
If your encryption key generation security depends on people not knowing how you generate keys, then it's totally busted.
Not always the same.
Re: Visual Studio and Team Foundation Server will have Git support
#113Earlier quoted context omitted.
As a (now former) long time Window developer, and even though people like to bash on it, I still think VS (>2003) is the best god damn IDE I've ever used. And with .NET it leaves everyone in the dust, IMHO.
You've obviously never suffered a large project. Crashes, memory gobbling, random debugger failures, glacial speed, lag, project configuration corruption, UI glitches, refusing to load projects, half complete refactoring operations, search/replace just stops, having to reset environment at least once a day, grey screen of death. And that's just the IDE. CLR is the only framework and language combo I've used which wil…
Re: Visual Studio and Team Foundation Server will have Git support
#114Re: Visual Studio and Team Foundation Server will have Git support
#115Rock on, Microsoft — this is great news for Windows developers. As much as the open source community (of which I am a part) loves to rag on Microsoft, they seem to have recognized the threat of platforms moving off of Windows (Steam, iPads, Android, ...) and are taking reasonable steps to encourage development for Windows (make the developer experience better). This — a reasonable response to a potential threat — is…
As a (now former) long time Window developer, and even though people like to bash on it, I still think VS (>2003) is the best god damn IDE I've ever used. And with .NET it leaves everyone in the dust, IMHO.
I find it slow, buggy and quite unfriendly. My guess is that people pay money for plugins to get it fit for purpose.
IDEs I prefer: Eclipse, Netbeans, IntelliJ, QtCreator
Re: Visual Studio and Team Foundation Server will have Git support
#116Re: Visual Studio and Team Foundation Server will have Git support
#117Earlier quoted context omitted.
You've obviously never suffered a large project. Crashes, memory gobbling, random debugger failures, glacial speed, lag, project configuration corruption, UI glitches, refusing to load projects, half complete refactoring operations, search/replace just stops, having to reset environment at least once a day, grey screen of death. And that's just the IDE. CLR is the only framework and language combo I've used which wil…
Yes, agreed (having worked on middlish-big projects with maybe 40 VS projects for each solution, 45+ minute re-compile times (not from scratch) on the latest gen CPUs, etc) with several hundred million LoC but believe me, if you think that's bad, you don't want to see Eclipse/NetBeans/XCode/etc. with a project a thousandth of that size.
Even if you have a reason to have 40 projects in what should looks like one solution you can still create various solutions files with just the subset of projects you need. No one works on 40 projects at the same time.
Re: Visual Studio and Team Foundation Server will have Git support
#118Earlier quoted context omitted.
Yes, agreed (having worked on middlish-big projects with maybe 40 VS projects for each solution, 45+ minute re-compile times (not from scratch) on the latest gen CPUs, etc) with several hundred million LoC but believe me, if you think that's bad, you don't want to see Eclipse/NetBeans/XCode/etc. with a project a thousandth of that size.
I know nothing about nothing, but having that many projects under the same solution its the biggest clue that you are doing something very wrong. Even if you have a reason to have 40 projects in what should looks like one solution you can still create various solutions files with just the subset of projects you need. No one works on 40 projects at the same time.
Re: Visual Studio and Team Foundation Server will have Git support
#119Earlier quoted context omitted.
You've obviously never suffered a large project. Crashes, memory gobbling, random debugger failures, glacial speed, lag, project configuration corruption, UI glitches, refusing to load projects, half complete refactoring operations, search/replace just stops, having to reset environment at least once a day, grey screen of death. And that's just the IDE. CLR is the only framework and language combo I've used which wil…
Yes, agreed (having worked on middlish-big projects with maybe 40 VS projects for each solution, 45+ minute re-compile times (not from scratch) on the latest gen CPUs, etc) with several hundred million LoC but believe me, if you think that's bad, you don't want to see Eclipse/NetBeans/XCode/etc. with a project a thousandth of that size.
I ask because I've never even come close to touching a project with that many SLOC and I was also under the impression that most modern operating systems are barely fitting into 100million+ LoC category, correct? This is your chance to redefine my perspective on "big project" haha.
Re: Visual Studio and Team Foundation Server will have Git support
#120Earlier quoted context omitted.
I'm curious, what Java IDE is 10K miles ahead of Visual Studio 2012/C# in your experience? Have you recently used VS with C#?
Java just doesn't scale, if you want fast code you wont use java. C++ one of the best, and for quick development c#, you can always invoke C++ libs in C# anyway and both are supported in visual studio. If your into webdevelopment even there java is slow.. despite it has some fun libs, but most people use them because their lazy programmers, a good programmer wont rely that much on much external libs
So a good programmer reinvent the wheel whenever he can?