DigitalOcean droplet console rewritten in Go

The only thing I can think of: net/http doesn't hide details but instead allows you to supply your own socket from which to accept connections, which in turns makes it possible to implement zero-downtime restarts with the help of packages such as goagain.

I was asking myself exactly the same thing.

I posted on reddit about how you could build this using open-source components: http://www.reddit.com/r/golang/comments/23zjxr/new_super_fas...

tl;dr use noVNC in the frontend and the websocket proxy bit is easy.

If there are people out there who are trying to choose a single language to learn, comments like yours should be a wakeup call to them:

Different situations and tasks call for different tools. Excelling in a modern development environment means being able to work with a variety of tools and being able to identify which tasks require which.

Static typing is an additional contract on the behavior of the code, similar to unit tests but built into the language itself and therefore cheaper to write. The overhead of specifying types slows you down during initial coding, but the code that results is more reliable and easier to read and maintain.

In environments where initial coding speed matters more than long term efficiency dynamic typing is preferable. Prototyping, mvp's, these are things that fit well into a loosely typed language. When that MVP grows into a business however, eventually it becomes benefecial to switch to static typing. Performance of a feature is usually the leverage that makes it happen, but the reduced cost of maintenance is what makes it stick.

So, both choices can be right for the same team at different stages of the product lifecycle.

What is interesting about Scala, go and rust is that they try to reduce the coding cost of static typing as much as possible (compared to Java, c and c++), giving the benefits without costing as much up front.

Because performance matters. And it matters more when trying to scale.

Scripting languages are really good for fast prototyping which helps in reducing the time to market which is critical for startups. When they go big, usually their codebase also goes bigger. Then they will start looking into maintainability, performance and 'ability to refactor' aspect of codebase. Statically typed language shines here and hence the move.

The documentation on the Go site is really good. You don't need much more than that. The early access book from Manning is really good so far (http://www.manning.com/ketelsen/) but it's only a few chapters finished. After that I find myself reading the source for the code in the standard lib which is well written and relatively easy to follow.

On the surface, that sounds reasonable. However, the Go platform has been very stable since 2012. Since Go documentation is standardized, learning how to write the language and use a few simple libraries (which a book from 2012 should do) should enable you to work with anything thrown your way.

I'd heard they were a heavy perl shop, but that might have been more backend stuff than frontend stuff.