"but he didn’t learn his lesson there"
This set me up for a negative article about Go, but, like other Go-related materials, it makes me want to use it. I should use it.
From Node.js to Go
11–20 of 192 posts
Re: From Node.js to Go
#12> Go is a compiled language so distributing applications for use on multiple platforms is just easier.
How is this a true statement? Ease of distribution isn't a function of a language's runtime environment (native vs interpreter).
Re: From Node.js to Go
#13Go is definitely promising but the last time I checked the problem with web development with Go was that there is no mature libraries for User authentication etc(Please correct me if I'm wrong). This makes going with Node or something like Rails more tempting.
Checkout Negroni [1] for middleware configuration combined with restgate [2] [1] https://github.com/codegangsta/negroni [2] https://github.com/pjebs/restgate
Negroni looks interesting. I saw there is a middleware called permissions2 that have some nice features. Will check that out, thanks!
Re: From Node.js to Go
#14> Go is a compiled language so distributing applications for use on multiple platforms is just easier. How is this a true statement? Ease of distribution isn't a function of a language's runtime environment (native vs interpreter).
They just mean static compilation, the program is a single file with all dependencies linked inside it.
Re: From Node.js to Go
#15> Go is a compiled language so distributing applications for use on multiple platforms is just easier. How is this a true statement? Ease of distribution isn't a function of a language's runtime environment (native vs interpreter).
Presumably he's talking about statically linked binaries.
Re: From Node.js to Go
#16I wish a language with advanced types like Haskell or OCaml would have the same tooling and ease of distribution around it that Go does. I haven't built anything in Haskell/ML in a while, so if anyone has any updates on this please chime in.
Re: From Node.js to Go
#17For me the single biggest disadvantage of Go against Node.JS is the lack of a decent dependency management solution. NPM is awesome and Go doesn't even have a "meh" answer to that.
What problems have you had managing dependencies with Go? I use Godep to vendor each dependency and rewrite import paths to use the vendored package. I found it to be an easy and effective solution.
Re: From Node.js to Go
#18For me the single biggest disadvantage of Go against Node.JS is the lack of a decent dependency management solution. NPM is awesome and Go doesn't even have a "meh" answer to that.
I feel and share your pain. I dislike the model of having to vendor in every third party library's source code, so I'm trying to build an alternative tool to Godep[1]. It's still a work in progress but the basic functionality is there :)
Re: From Node.js to Go
#19I wish a language with advanced types like Haskell or OCaml would have the same tooling and ease of distribution around it that Go does. I haven't built anything in Haskell/ML in a while, so if anyone has any updates on this please chime in.
You can use this (https://halcyon.sh) for Haskell. Still not the same though.
Re: From Node.js to Go
#20I wish a language with advanced types like Haskell or OCaml would have the same tooling and ease of distribution around it that Go does. I haven't built anything in Haskell/ML in a while, so if anyone has any updates on this please chime in.
You may wish to explore Rust - http://www.rust-lang.org/. I can't speak to tooling but it has advanced typing and ease of distribution seems similar to Go.
Edit: mea culpa for my attempt at tongue-in-cheek humor, "I think that's called Rust - http://www.rust-lang.org/"