Ask HN: Building a large webapp today - what language for the backend, and why?
41–50 of 64 posts
Re: Ask HN: Building a large webapp today - what language for the backend, and why?
#42Use a higher level programming language and use a standard interface to communicate with the frontend. If you build a REST API for the backend it doesn't even matter what language it is written in. You can always swap parts out for faster performing versions later on. You can even split up parts in different programming languages. If you want to decrease development cost go with an ecosystem that most of your develop…
Re: Ask HN: Building a large webapp today - what language for the backend, and why?
#43Re: Ask HN: Building a large webapp today - what language for the backend, and why?
#44Re: Ask HN: Building a large webapp today - what language for the backend, and why?
#45Earlier quoted context omitted.
I take it that it's not popular around here because this site is full of Apple lovers, but there is not denying that C# is 'Java done right/better', so I really see no reason to use Java over C#. Furthermore C# has the best IDE in the world (Visual Studio), it has a lot better performance than Ruby for instance, it has a sublime integration with web services/databases/etc., it has great documentation (MSDN)...
A lot would argue that it's a horribly cluttered and slow IDE. People who love VIM will definitely not like Visual Studio. That said, since the last few years Microsoft has really been on top of their game. Their latest frameworks are easy to grasp and perform very well. C# is also not too verbose and on top of that they are starting to push open-source with initiatives like codeplex and NuGet. In their MVC Framework…
Re: Ask HN: Building a large webapp today - what language for the backend, and why?
#46Re: Ask HN: Building a large webapp today - what language for the backend, and why?
#47I started my business exactly a year ago this month. My co-founder and I went with Java on the backend for a few reasons: 1. This is what we were most experienced in. It is important to use what you know in a lot of circumstances because otherwise you'll have a harder time getting off the ground with your projects. Sure, Java isn't hip/cool in a lot of circles, but it gets the job done and there is a ton of support f…
Re: Ask HN: Building a large webapp today - what language for the backend, and why?
#48Earlier quoted context omitted.
This is the first time in my life I've seen someone defend C# and .NET. I don't know that I've been looking very hard though.
I take it that it's not popular around here because this site is full of Apple lovers, but there is not denying that C# is 'Java done right/better', so I really see no reason to use Java over C#. Furthermore C# has the best IDE in the world (Visual Studio), it has a lot better performance than Ruby for instance, it has a sublime integration with web services/databases/etc., it has great documentation (MSDN)...
I see plenty and I've done both and stuff that existed before Java or C# either one existed like C++, C, BASIC and Assembly.
Re: Ask HN: Building a large webapp today - what language for the backend, and why?
#49Earlier quoted context omitted.
This is the first time in my life I've seen someone defend C# and .NET. I don't know that I've been looking very hard though.
I take it that it's not popular around here because this site is full of Apple lovers, but there is not denying that C# is 'Java done right/better', so I really see no reason to use Java over C#. Furthermore C# has the best IDE in the world (Visual Studio), it has a lot better performance than Ruby for instance, it has a sublime integration with web services/databases/etc., it has great documentation (MSDN)...
Re: Ask HN: Building a large webapp today - what language for the backend, and why?
#50Earlier quoted context omitted.
Some of it might have to do with the server platform - a lot of us really like the flexibility of using Linux on the server, but when we think C# we think IIS + Windows. Is the server-side ecosystem for Linux-hosted C# production worthy? And if so, does it compare well to the solutions getting recommended in this thread?
I wouldn't run .NET software on Linux, I'd just stick to Windows Server. It's really solid nowadays, and there is enough choice (it isn't even more expensive than linux hosting). Check out Azure and AppHarbor for cloud hosting for example: they both work extremely simple, and have powerful capabilities.
A specific comparison would be nice, blanket statements are not helpful.