Earlier quoted context omitted.
Dream on. Java ecosystems have left you guys by 10k miles.
I attempted to write a simple web project in Java to learn it. I haven't used Java before, I normally use Python for web stuff and C# for other misc stuff. It was hell. I installed JetBeans IDEA quickly enough, but it went downhill from there. My AntiVirus (Kaspersky) fucked with Java 7's networking meaning it couldn't connect to anything, so it took an hour and a lot of googling to fix that. Next step: make a struts…
Visual Studio and Team Foundation Server will have Git support
181–190 of 220 posts
Re: Visual Studio and Team Foundation Server will have Git support
#182Cool - when will Windows support the 'fork' call? If they do that and support the '/' as a path separator (which was always there), Windows might get a resurgence.
Re: Visual Studio and Team Foundation Server will have Git support
#183Earlier 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'm pretty sure I've read on an msdn blog that visual studio was 100 million loc total. I would be very curious to know what kind of projects you're working on.
Re: Visual Studio and Team Foundation Server will have Git support
#184Cool - when will Windows support the 'fork' call? If they do that and support the '/' as a path separator (which was always there), Windows might get a resurgence.
Windows has a POSIX subsystem. It has fork. Not cygwin style. There is kernel support.
Re: Visual Studio and Team Foundation Server will have Git support
#185Earlier quoted context omitted.
VS is the only large scale IDE I know of that refuses to add a search bar for options. Both Eclipse and Intellij IDEA both have it. Trying to deal with finding what you want in the myriad of options VS has is tedious. Also changing syntax colorings without something like resharper is also taxing.
This exists in 2012 now. http://www.dotnetspark.com/kb/5328-whats-new-search-options-...
Re: Visual Studio and Team Foundation Server will have Git support
#186If MS had tried to make a DVCs to compete with git, they would have always been third-fiddle (to git and Mercurial, and possibly others). But they could still have made money selling it to all-Microsoft shops.
Instead, they acknowledged the situation and incorporated git support!
This is so right, so beneficial to their customers, and yet so completely opposite to what I expected them to do!
I must give credit where credit is due ... fantastic decision, Microsoft!
Re: Visual Studio and Team Foundation Server will have Git support
#187Earlier quoted context omitted.
In what way? What things are you comparing? All I know is that the next version of Java will have features inspired by the last version of c# http://mail.openjdk.java.net/pipermail/lambda-dev/2011-Septe...
C# tools and libraries have been inspired by Java since the inception. I'll give C# a +1 for lambda/functional feature but the rest does not equal +1. MSBuild -> Ant NuGET -> Ivy DoesNotExist -> Maven (don't forget to count maven plugins). NHibernate, Log4Net, etc -> inspired by its Java counterpart. How about sane deployment/packaging system? WAR, JAR, EAR push to App Server (tomcat, glassfish, etc). Not so easy wit…
Re: Visual Studio and Team Foundation Server will have Git support
#188Earlier quoted context omitted.
In what way? What things are you comparing? All I know is that the next version of Java will have features inspired by the last version of c# http://mail.openjdk.java.net/pipermail/lambda-dev/2011-Septe...
C# tools and libraries have been inspired by Java since the inception. I'll give C# a +1 for lambda/functional feature but the rest does not equal +1. MSBuild -> Ant NuGET -> Ivy DoesNotExist -> Maven (don't forget to count maven plugins). NHibernate, Log4Net, etc -> inspired by its Java counterpart. How about sane deployment/packaging system? WAR, JAR, EAR push to App Server (tomcat, glassfish, etc). Not so easy wit…
The original C# language and virtual machine was inspired by Java.
Then, C# got: * Better generics
* lambda expressions
* the yield keyword and compiler magic for iterators
* explicit interface implementation (rarely needed, but very well thought-out for when you need it)
* LINQ!!!
* Type inference
* Dynamic keyword
(I'm forgetting some things, it's late).
Anders has guided the C# language brilliantly ... Java has been outpaced at every step of the way. So many somewhat radical features have been added to C#, and from my standpoint, every single one of them was very well-done.
Re: Visual Studio and Team Foundation Server will have Git support
#189Git doesn't transplant from the UNIX ecosystem very well. It's why the only options for Git in Windows so far have been as part of a UNIX interop solution like msys, cygwin, interix, etc. It will be really nice to see a proper Git client for Windows especially if it means Windows is also getting a proper SSH.
Git on Windows works fine for me, no cygwin in sight. It wouldn't have occurred to me to call msys 'part of a Unix interop solution', though I suppose it does give me a working version of Perl, which is a feature since it was the occasion for me to start using ack instead of grep.
> MSYS is a collection of GNU utilities such as bash, make, gawk and grep to allow building of applications and programs which depend on traditionally UNIX tools to be present.
Re: Visual Studio and Team Foundation Server will have Git support
#190Earlier 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.