My Opinionated Guide To Go • Hacker News Board

Re: My Opinionated Guide To Go

#71

Post by wtbob » Fri, May 16, 2014, 5:39 AM UTC

lateefj wrote: post #57

rthomas6 wrote: post #5

Why does this article only compare Go with interpreted languages at the top? Go is a compiled language; wouldn't it be more fair to compare it with other languages that can be compiled, like C++, Rust, Haskell, or Lisp/Scheme? I mention this because the article acts as if getting rid of abstraction layers between the OS and the code is a new idea. No, that's how all compiled languages are... that's the point of compi…

Author here. I was comparing things that I have developed software in. It would seem unfair to compare things that I have not actively contributed production code and deploy. I mainly write web applications (services) of which C++, Rust, Haskell or Lisp/Scheme are not languages I find compelling to write web applications with. Would love to hear if you find this otherwise.

There are some nice things about writing web apps in Lisps, since one can represent HTML as s-expressions, e.g. (:html (:body ((:p (:class "main")) "Foo bar baz."))). And of course macros mean that one can create nice abstractions quite difficult or impossible in other languages.

Re: My Opinionated Guide To Go

#72

Post by regularfry » Fri, May 16, 2014, 2:27 PM UTC

lateefj wrote: post #55

regularfry wrote: post #53

Earlier quoted context omitted.

The question he's addressing isn't what you can do, but what is commonly being done. You don't need RVM, you don't need Docker. Hell, you don't need Rails. But those are the idiomatic layers of the stack, for a non-trivial part of the Ruby development community.

Sorry for the confusion JVM = Java Virtual Machine, RVM = Ruby Virtual Machine, PVM = Python Virtual Machine. What I was trying to point out the layers of vitalization just to run an application. Docker is yet another layer on top of the operating system (a virtual machine running inside an operating system inside an operating system possible ect).

Ah, ok. I can see where you're coming from, but I don't really think of Docker as being an extra layer on top. It's more a way of rearranging the OS layer itself along a certain axis. The cognitive overhead is similar to a virtualisation layer though, so that point stands.

Re: My Opinionated Guide To Go

#73

Post by regularfry » Fri, May 16, 2014, 3:56 PM UTC

icebraining wrote: post #59

regularfry wrote: post #53

Earlier quoted context omitted.

The question he's addressing isn't what you can do, but what is commonly being done. You don't need RVM, you don't need Docker. Hell, you don't need Rails. But those are the idiomatic layers of the stack, for a non-trivial part of the Ruby development community.

Docker is used by a non-trivial part of the Ruby community? I find that hard to believe.

Non-trivially noisy, perhaps.