201–210 of 220 posts
Earlier quoted context omitted.
I could pick those up one by one, but time does not permit. You are largely correct that there seems to be more experimentation in the the java open source ecosystem, and that some of the key parts of the same in .Net are ports from java (e.g. nUnit, log4net, nhibernate). Though in all those cases there are alternatives, it's just that the particular tool mentioned is most popular. Possibly due to familiarity. With m…
Sir, Maven is an awesome thing. Would you want me to do a query in Google for each and individual .net and the word "sucks"? Since when that matters? There will be minorities that just happened to dislike everything. There are also people who just happened to use maven in the wrong way and ended up fighting with it. This suggests that you have never used and experienced Maven. Combined eclipse with m2clipse and you w…
I don't know maven from a bar of soap, but would you diagree with this recent hn post then? "Why Everyone Eventually Hates or Leaves Maven" http://news.ycombinator.com/item?id=5105164
Now I've had a look at the basics of what Maven does ... http://en.wikipedia.org/wiki/Apache_Maven " It can also be used to build and manage projects written in C#..."
Honestly, if it was that far beyond everything else, people in the .Net community would be talking about it a lot. And they're not.
> Imagine not having to download 3rd party library manually by visiting their website. Imagine autocomplete of the freshly acquired 3rd party lib via your IDE to also shows you the javadoc. Imagine trying to navigate to the 3rd party class and method implementation without setting up your IDE or messing with path/folder setup automagically. You cannot do any of these in .net nor vs.net.
Factually incorrect. The equivalent happens in VS via nuget right now.
Earlier 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.
Dream on. Java ecosystems have left you guys by 10k miles.
Apart from the low jab in this particular line, why's Java related to VS, VS features and the .Net eco system?
Language wars are boring.
Earlier quoted context omitted.
I think you first have to ask why Microsoft is supporting git when Team Foundation is, itself, Microsoft's primary source control system. The answer is most likely because people use git. Lots of people use git - particularly the crowd Microsoft is actively struggling to appeal to which is the entrepreneurial/startup crowd. I've never used hg so I can't attest as to which is "better" but I really don't think that mat…
The OP is simply saying that it seems odd that Microsoft would pour $20,000+ into Mercurial and then add git support to VS. http://mercurial.selenic.com/sponsors/ I'd bet this is simply a case of the right hand not knowing what the left hand is doing. I had no idea Microsoft were sponsoring Mercurial--even that seems odd, spending money on an open source competitor to a product they also make. I think your analysis i…
But developing OpenSource software in Windows is still a pain: You still need Make, GCC, Autotools, etc. etc. and even if you can install Cygwin it's messy as hell. And powershell sucks, we don't need another shell: we have been using Bash for decades.
But 'Bash for decades'? Is that true? A quick search for bash 1.0 shows me tarballs from '95, which isn't yet decadeS old.. Ignoring the question of whether bash is the optimum shell and that some systems migrated to replacements (think dash, all the zsh lovers).
So that last line of yours seems a little over the top.
But developing OpenSource software in Windows is still a pain: You still need Make, GCC, Autotools, etc. etc. and even if you can install Cygwin it's messy as hell. And powershell sucks, we don't need another shell: we have been using Bash for decades.
Earlier 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.
Here's the link: http://blogs.msdn.com/b/visualstudio/archive/2012/06/20/the-...
This line caught my eye:
"Some of its benefits fit well with the trends we see in software development: loosely coupled systems, distributed teams, lots of component reuse, incorporation of OSS, etc."
It's not a new trend. Nevertheless, I'm smitten that MS has acknowledged and embraced the model.
For us, the biggest issues with git on windows are:
1) SSH inconsistencies (cygwin/putty/msysgit/securecrt/etc) - I support users that use any combination of these.
2) Git implementations (cygwin/msysgit/git extensions/etc) and UIs all handle git and SSH differently. Users will typically have multiple copies of git installed and used, depending on context.
3) Support for HTTPS mode is inconsistent and in some cases non-existent. None of them can cache credentials.
To summarize; multiple git environments + multiple SSH environments + limited https support = pain.
Earlier quoted context omitted.
Ok, so what we're really saying is, I want a vt100 emulator.
What I'm really saying is I want a terminal, in which I can run whatever shell I want. See also: Unix, Linux, OSX, etc, etc, etc.
* get far enough along in my code that I want to check in, launch VMWare Fusion, start Windows, login to Windows and run security updates, connect card reader, login to the VPN, oops bad password, login to the VPN again, more security updates, launch Visual Studio, connect to TFS, launch project solution file, check out my project, find the local directory on Windows where the files are stored, copy files from Mac to Windows, check in the project. Cry a bit.
And THEN: a couple hours after Git integration was announced, we moved a project I was working on over to Git on Team Foundation Service.
My new workflow:
* Make a change in the code, commit, pull, push. From INSIDE Emacs on my Mac. If you didn't know any better, you'd think I was just pushing code to GitHub.
In short, I love you.