Live data from Hacker News

Ask HN: What are the best technologies you have worked with in 2013?

news.ycombinator.com

31–40 of 46 posts

Re: Ask HN: What are the best technologies you have worked with in 2013?

#36

You're going to hate this answer, but after a couple of years of Node/Express development I'm really enjoying writing Asp.NET in C# using Visual Studio 2013.

I have been using Microsoft technologies for many years, and I don't believe I will change it. Microsoft technologies are quite mature.

Re: Ask HN: What are the best technologies you have worked with in 2013?

#37

Earlier quoted context omitted.

the world has moved over to javascript I'm not so sure about this. Python and Ruby seem to be just as popular as Node (if not more) for new projects, and as far as older projects go, PHP is still king.

My experience with Berlin startup scene is that Node.js took its niche and its popularity is not growing so rapidly now. There are more projects in Ruby and Python. I see there are couple more Scala jobs appeared and even saw 1-2 in Go.

I am wondering how you are tracking Berlin wanted technology stack?

Re: Ask HN: What are the best technologies you have worked with in 2013?

#38

You're going to hate this answer, but after a couple of years of Node/Express development I'm really enjoying writing Asp.NET in C# using Visual Studio 2013.

Web Forms or MVC?

He says he's enjoying it, so it must be MVC.

Re: Ask HN: What are the best technologies you have worked with in 2013?

#40

You're going to hate this answer, but after a couple of years of Node/Express development I'm really enjoying writing Asp.NET in C# using Visual Studio 2013.

I'd love to hear your reasons for this, as I've been looking at moving away from the Microsoft stack. Thanks!

I like the IDE (a lot). I'm not reinventing anything, just doing web development. Visual Studio gives you every tool you need to get the job done in one package that's frequently updated and runs stably and consistently (on my machine). The individual tools may not be better than their OSS equivalents, but as an overall ecosystem they are fairly well-tested and work together extremely well in my experience. NuGet is very cool and easy to use.

The end result for me has been that I spend significantly less time wondering why things aren't working (almost none, really) and more time actually writing and improving my code.

If you are doing something groundbreaking or way-out-of-the-box, Visual Studio is probably not a great choice. But for workaday web developers like me it's reliable, easy, and has objectively made me more productive compared to Node/Express/Backbone.

Post reply on HN