Ask HN: What are the best technologies you have worked with in 2013?
31–40 of 46 posts
Re: Ask HN: What are the best technologies you have worked with in 2013?
#32Combines the solver goodness of modern SAT and CSP solvers with the modeling-language richness of classic Prolog.
Re: Ask HN: What are the best technologies you have worked with in 2013?
#33Re: Ask HN: What are the best technologies you have worked with in 2013?
#34You'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.
Re: Ask HN: What are the best technologies you have worked with in 2013?
#35Re: Ask HN: What are the best technologies you have worked with in 2013?
#36You'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.
Re: Ask HN: What are the best technologies you have worked with in 2013?
#37Earlier 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.
Re: Ask HN: What are the best technologies you have worked with in 2013?
#38Re: Ask HN: What are the best technologies you have worked with in 2013?
#39Re: Ask HN: What are the best technologies you have worked with in 2013?
#40You'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!
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.