C# is a great language, and there are several libraries with fantastic design aesthetic; one that is much better than most of Ruby/JS.
It's painful when you have to go into your IDE, step through a bunch of stuff, just to make a small change, and then a couple minutes goes by before you can check your work. Integrate some larger testing, and it's worse.. try to break you project up into smaller libraries (as you would with node) and it gets worse.
Don't get me wrong, I really like C#, and love the Razor view engine... but .Net and VS as a whole just feel really sluggish and bloated. With node, I can fire up an app, and include modules with relative ease.. I don't get the same level of intellisense as VS with C#, but I find I need it quite a bit less, and tend to be just as, if not more productive.
I started with C# in mid 2001 (before VS.Net RTM), and until Node.js it was by far my favorite environment.
Kind of like how Rails devs have tests that run for minutes?
I kid. Sort of. Both instances are problems of poor design and architecture. C#/VS don't really pay off until you start having larger code bases. Which, for web apps, doesn't happen...until it does, and then it sucks. The semantic analysis afforded by more static languages like C# becomes a real boon then. I'm not going to argue that types will fix the Software Problem, but they do help considerably, especially when an API shifts out from under you.
I love VS (and won't write any C++ without it), but it is pretty hefty. Some of the recent UI changes are highly questionable in my mind, but, that's MS for you.
It's about learning your tools, and how to bring in what you need, and keeping out what you don't. In the end it's almost as much about technique as the tools, but sometimes it's easier to adopt new techniques while adapting to new tooling.
Also, a lot of script-y environments discourage you from thinking about it: Rails' autoload, DHH's rants, no compilation/linking step, etc.
Now, we promote such a way in the name of productivity. Little wonder SRP gets squeezed out.
Also -- F# is completely open-source, so there's no "Microsoft tax" to be paid. In fact, a large portion of the F# community runs exclusively on non-Windows platforms (e.g., OS X, Linux, FreeBSD, Android).
For example its easier to get started with F# with MVC on the Xamarin IDE then it is in VS. Hope it takes off.
I mean, C# is a fantastic language, but a lot of the libs MS has bundled into it are absolutely horrible and people use them anyways because they're the blessed first-party product. And rather than fixing the problems, Microsoft simply creates a new replacement lib with a new approach. I mean, how many kicks at the can did they get with remoting? DB access? Serialization?
Microsoft has gotten a lot better recently, taking an open-source-style development approach to Entity Framework and MVC, but they're very late to this particular party.
.NET has been around for a long time, long enough to have gone through the rise an decline[1] of many open source alternatives:
DHTML, PHP, Python, RoR, NodeJs
And the language and framework has been thoughtfully improved over that period of time.
> Microsoft's bloated and broken enterprise tools instead of sensible, rapidly-released libs.
Developers have been writing great software with these tools for decades.
And rapidly-released libs could just as easily be classified as "not-yet-ready-for-production."
> I think the big problem is that MS
In my estimation, the biggest problem is that using .NET "requires" the rest of MS along for the ride. Yes you can use mono, yes you can use apache, but everything just works if you use the WINS stack.
I like .NET and I really like C# as a language, but I'd rather have my infrastructure be linux.
[1] Not all of these have "declined", but popularity has shifted focus.
But where other libraries would have to compete in the open market-place of ideas, Microsoft's failures are still "blessed" by MS and so we still use them.
But the bigger frustration is that they don't seem to really properly iterate on the libraries. They get fired out as part of a .NET major version release and get at most minimal bug-fixes beyond that. If there's a major flaw in the lib, it will not get fixed. Instead, a completely new library with its own flaws and a whole new learning curve will appear, and the old lib will remain and languish in its "functional but still fundamentally frustrating" state.
Like I said, I'm ecstatic to see that MS has moved away from this methodology with Entity Framework - they've de-coupled it from the .NET core and are iterating on it faster than Once Every Major Language Release.
I've decided for my own side projects to start using Django and Postgres.
I can be pretty much be confident that two years from now whatever version python, Django and Postgres are, my gained experience and knowledge will still be very relevant as the maintainers of these projects don't have a mandate of building a brand new API, or what have you every year.
This is definitely changing with NuGet: Immutable collections, OWIN, SignalR, etc.
Async/await really is a great abstraction on top of task parallelism; it's easy to understand without having to wade through a zillion blog posts explaining how it's just like burritos, Lego blocks, the OSI model, or homeobox genes, or underpants. Which means that it's something you could actually get away with using in enterprise software development, rather than something that'll earn you a reputation for developing software that your colleagues wouldn't be able to maintain.
I have to disagree to you also on the ground that almost everything in Haskell is (and many important things in Erlang are) async without any annotations. Haskell is lazy and that alone makes many operations "asynchronous", so to say. It's run-time system is heavily threaded and employs work stealing to fit millions of green threads into several system threads.
You can write your own scheduler [1] for your purposes, if you please. As fine grained as you want it to.
[1] http://hackage.haskell.org/package/meta-par
In fact, .Net is years behind of Haskell and Erlang. Just because it borrows features from Haskell (and other languages) libraries and bolts them into language.
The difference here is that things in libraries are first-class, you can create them at run-time. That does not often apply to language constructs.
thirsteh's cynicism is misplaced. node.js is effectively predicated on asynchronous implementations, and you have to work hard to do otherwise. The end result tends to be very efficient implementations that can serve large numbers with ease. .NET bolted on asynchronous sugar as it matured, and while that is very good, and you can make efficient implementations, most don't. So it's not really reasonable to dismiss the talk about one because it's possible in another.
EDIT: thirsteh is continually editing their posts so assume their commentary is very different from what it originally was.
Despite what you seem to imply in your comment, I/O does not block an entire thread in any of these languages, however the control flow in a single thread does block, i.e. err = fireTheRockets() does block until fireTheRockets completes, but performance-wise it is equivalent to fireTheRockets(function(err) { ... }). Only now you're saved the callback spaghetti.
Node.js advocates are literally peddling callback spaghetti as an advantage because "it lets you write much faster applications with ease", yet Haskell's threads and blocking semantics blow any Node.js out of the water by an order of magnitude. (Check out Mighttp/Warp or Go's net/http vs. Node.js.) I come across as cynical because that is sad. It feels like we're travelling back in time, not forward.
The only thing that makes node.js "good" when it comes to threading and async is that it doesn't require synchronization as there is no concurrency. (Same thing for Python with Twisted.) Neverminding that that opens up its own can of worms (I hope you don't do any actual computation in your program, as that's going to block everything): Pretending that it's anything more than that comes across as incredibly ignorant of contemporary language design.
And you would lose.
This conversation was about .NET, and then you (rather oddly) decided to pull in nodejs. It has nothing, at all, to do with Erlang, Go, Haskell, or any other language, and the tactic of using them as the "big brother" to discount another language is petty and disingenuous.
The reason I mentioned those languages is that there is essentially no way (short of using the C ABI) to actually do blocking I/O. It doesn't mean that you can't write performant asynchronous programs in C#.
Maybe you should knock that nodejs chip off your shoulder and get over it. Clearly you had some sort of argument with someone about it at some point, but your arguments just make you look absurd.
Here is what you said: "thirsteh's cynicism is misplaced. node.js is effectively predicated on asynchronous implementations, and you have to work hard to do otherwise. The end result tends to be very efficient implementations that can serve large numbers with ease."
This is what I responded to. Your statements are simply not true. And no, I wasn't the one who brought up node.js either.
My gripe with node.js is that it claims to be something much greater than it is, and people gobble it up. If you want to write Javascript, sure, it's a great tool. Just don't try to sell it as the only, or even a good way to write fast applications. That is what is disingenuous.
Your quote comically excludes the preceding paragraph about .NET, and the following sentences specifically contrasting .NET with nodejs. Instead you continue this transparent charade of pretending that I said something that I didn't.
This boring side discussion is done. You have said absolutely nothing of value, but should feel relieved that you took a irrelevant shot at nodejs for no particular reason.
I do, however I fear it will do very little to stem the tide of frontend developers discovering the awesome powers of asynchronous callbacks in Node.js, and continuing to repeat the meme that it is the best way/a good way to write fast applications. Every other thread on Hacker News is about Node.js these days.