Horusiath

WTF? You're moaning, that the systems programming language invented over 40 years ago has no means for automatic memory allocation management and high level abstractions. Sorry but this is just crappy post.

it's (k-1)^2 actually - each to each except self.

Don't confuse Mono and Xamarin, they're two separate things.

Taking from the author's paragraph:

- Emacs - Java IDEs may look better, but this doesn't seem to be an issue for author. Also other tools are very mature for such youn language as Go.

- Goroutines - Java has no built-in equivalent or one opinionated way of green-threading, only frameworks requiring months of expertise. From perspective of person, who need to switch language quickly this is very discouraging.

- No inheritance - Java design patterns are clearly no-no in the described context (they were presented as anti-pattern).

- Built-in, effective templating - again one easy path to start with, also powerfull enough to write your own tools if needed.

Go is simply easier/faster to start with and most of the performance problems were not GC-bound, so JVMs maturity wasn't such an advantage.

1. Basic misconception - being JS developer doesn't make you a node.js developer. 2. Blogpost makes an assumption than node.js could be used for enterprise software development and shows page serving metrics as a proof. Actually IMO most of the enterprise apps are not about page serving - there are a lot of them used only by few hundreds of people in 9-17 daily basis. Backend business logic is a lot more important and the post doesn't proof in any way, that using node would be proficient in that matter.

This looks more like flame war starter, than post with any essential argumentation. tl;dr - "I've tried to write C# code in F# and I think that writing it in C# is better."

Why? This is exactly what type definition describes - an array of string or numbers. If you'd like to have an either array of strings or array of numbers, you'd type: Array<string>|Array<number>

I actually like cleanliness of Javascript generated from Typescript code. However I don't think that pattern matching would be more intrusive than, for example, module or class generation. Basically example from above could be compiled down to something like:

    var x = getResults();
    if(x instanceof Error) { ... }
    else if(x instanceof Results) { ... }

Tell that next time you get on the plane.

Actually this is not Developer vs. Consultant, but rather Coder vs. Developer comparison. Consultant (which could also be a Developer) has nothing to do here.

I'm curious why ServiceStack.net has fall out so badly, since their own benchmarks shows a lot higher performance than ASP.NET web applications.

Just another day on HN and another trolling, controversial post...

I'm not a CS lover, but I think most of your arguments are invalid. You say that you don't like CoffeeScript because it generates JavaScript code you don't understand. But do you understand what machine code will JS generate? No? Why? Maybe because you don't care... In general same thing applies here. If you need to debug generated JS, use source maps. This argument is not an excuse. Beside, CS is fairly simple in translating to/from JS. If you think it's not, try use dart2js ;)

Sorry, but you are actually comparing features of GUI more than SCMs themself. Actually many of Git users don't use any GUI just because they don't need to. And when it comes to SCM features comparison, Git is a way better.

Sincerely, Perforce user.

"in Scala (via IKVM via MonoTouch)" first though: http://images.wikia.com/glee/images/6/6f/We-need-to-go-deepe...