4 ms·

Here a list of why OP's list of advantages of Go for web developers: * Static typing * Web sockets * Concurrency * Unit testing * Speed * Syntax * Forma

• pjmlp 11y ago
  My web development experience, apart from an experience with TCL that teached me never to rely on scripting languages for serious web applications, is on the JVM and .NET stacks. Both eco-systems fill all those bullet points.
  • vetinari 11y ago
    As someone, who is right now debugging an .ear, my preferences right now would have JVM or NET stack at the end, behind all scripting languages imaginable.
    • pjmlp 11y ago
      Using Java doesn't mean to use EAR files. Luckily I only had to use them on Websphere based deployments.
• cmdkeen 11y ago
  By night I might play with Django and like it. By day I make good money using C# where I get all of the above at what seems to be a much more web appropriate level than Go. One of the things that I'm really liking about the ASP.Net Core rewrite is that a framework that has been around for ages is taking an opportunity to look at what it does well, what it doesn't and what other languages / frameworks have innovated on more recently and stealing liberally. C# has been through several cycles of how to write concurrent code now and offers both Task and async/await depending on your needs. Not only is web sockets support there but SignalR is there as a useful API for common cases. If you want even better static typing you can switch to F#. Not everyone was doing web development using single threaded dynamically typed languages before Go came along.