111–120 of 235 posts
Earlier quoted context omitted.
"open source language" - such as F# or Clojure? Both don't require you to abandon the best IDE on Earth. http://visualstudiogallery.msdn.microsoft.com/0e53eaf6-b031-...
Whoa, didn't know about this. I'll check it out.
Earlier quoted context omitted.
Not running into those issues must be really great for you, but does very little to make the experience better for me. I tend to run VS under virtualization with TFS, which is far from a pleasant experience, even on modern hardware.
So on a local machine, in virtualization, you are running an IDE, SharePoint Server, SQL Server, IIS, TFS. If you aren't running it from a separate SSD drive then the problem has nothing to do with the IDE. You have an IO bottleneck.
That said, my experiences with Visual Studio only serve to underscore the point that my peers would prefer to avoid running a Windows VM altogether if there are open-source alternatives that are good enough.
Earlier quoted context omitted.
But F# is so much better that I can't think of a single reason for choosing C# over it.
I wish F# had first class support from ReSharper.
C# and .NET get a bad rap for being created by Microsoft. But one thing that can't be ignored is how polished their development tools are. I absolutely love coding in Visual Studio.
Personally, it's because Microsoft development locks you in, and costs a lot of money. The OS costs money, the server OS costs money, the database costs money, the IDE costs money, everything costs money, and you have to use it, for the life of your app. To many young developers these days, and IIS server is the thing your company keeps in the closet to some sluggish legacy monstrosity which has been replaced for yea…
Earlier quoted context omitted.
I believe you have an install issue.
Wouldn't that be nice? I'd be inclined to agree with you if it were just me or one machine, but these are characteristics that I'd use to describe Visual Studio across a number of machines, projects and teams over several years.
I find a 100project C# solution (200mb deploy) to be perfectly snappy when using & fast to build. There are and have been zillions of annoyances with VS but perf hasn't been one since I set my machine up properly (in the office most of the developers complaining about build perf could cut 75% or more just by excluding certain dirs from AV scan).
C# and .NET get a bad rap for being created by Microsoft. But one thing that can't be ignored is how polished their development tools are. I absolutely love coding in Visual Studio.
But F# is so much better that I can't think of a single reason for choosing C# over it.
One reason to favor C# is that it just has better IDE support, hands down. In addition, if I'm working with C# devs it's just nicer to use something everyone already knows.
As far as the language goes, though, perf sensitive stuff often makes more sense for me to do in C#. This is a combination of reasons:
1) I generally have a better sense of the IL that a given C# program will generate. This is both because I am a C# compiler dev and because C# is closer in form to the .NET IL than F#.
2) I have a better sense of the actual machine code that will be generated for C# code by the JIT. This is almost entirely because I am a dev on the C# compiler.
3) The language/framework teams are very data driven. The population of F# developers and F# code in comparison with C# developers and C# code is like a drop in the bucket. There are hundreds if not thousands of C# developers for every F# dev. It is almost a statistical certainty that C# JIT hot spots will get optimized before F#.
4) The fastest F# is usually very imperative and is essentially the same as the C# code.
Visual Studio could be so much more for Microsoft. Why do they need a phone? Let them make Visual Studio cross platform and developers would come back to Windows as their base platform. All other IDE's pale in comparison. Too bad that advantage is being wasted as far as new developers go.
I honestly can't imagine going back to the dismal experience that was the ecosystem I used in undergrad - Linux/Unix + Java/Ruby/Python/C/C++. The only one of those I actually still enjoy working in is Python, and I can do that on .NET in VS as well. Ruby/Rails isn't really that bad TBH, but these days it just feels like a second rate dynamic version of MVC.
As someone who has recently been hiring .NET engineers, I have to admit that this inspires mixed feelings. On the one hand, I can see huge power from combining AI and search with the structured context of programming. On the other hand, a disappointing number of the people we interviewed weren't software engineers, they were IntelliSync engineers. We'd give them a problem, and their first instinct was to hit a period…
I use dynamic languages and have never touched an IDE, but I still do this.
If I find out I need some feature provided by libfoo to accomplish a task, then, before I even look up the libfoo docs, I try this, or an equivalent:
require 'libfoo'
LibFoo.constants
(LibFoo::Foo.new.methods - Object.methods).sort.grep /bar/It will be quite nice if this ends up yielding results for individual JavaScript frameworks some day.
I'm one of the creators of Sourcegraph, which does have results for many JavaScript frameworks. You can find examples from all across GitHub, and you can search by function name or full-text documentation. JS is hard to analyze, but we're working hard on getting better--and the analysis code is open source[1]. https://sourcegraph.com/github.com/joyent/node https://sourcegraph.com/github.com/jashkenas/underscore https…
Earlier quoted context omitted.
VS lock in is a very real thing. At my current employer, there is no way they could ever come off of VS and .Net because of the lack of polyglots in the office. There is one of us that does Java, 3 that do PHP (only in the last 6 months), and 6 that are set up for .Net MVC. Management just can't spare the costs to retrain, and none of these guys go home and code on non MS platforms.
I could switch languages more easily than I could switch dev environment. The lock in to me is bssically simply that there aren't many other good language+IDE combos out there. There are plenty of languages that are interesting but very few come with a great IDE. I'd love to do Rust or Haskell all day, but I'm sure as hell not going to vim/emacs/sublime from VS. I almost envy those who never started using and IDE and…