From Node.js to Go

#1

Post by francesca » Thu, Jan 29, 2015, 8:05 PM UTC

Re: From Node.js to Go

#2

Post by drikerf » Thu, Jan 29, 2015, 8:36 PM UTC

Go 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.

Re: From Node.js to Go

#3

Post by [deleted] » Thu, Jan 29, 2015, 8:45 PM UTC

[deleted]

Re: From Node.js to Go

#4

Post by voidlogic » Thu, Jan 29, 2015, 8:52 PM UTC

drikerf wrote: post #2

Go 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.

>no mature libraries for User authentication

"User authentication" can mean 1,000 different things, maybe if you clarify your use case, people can suggest solutions.

Re: From Node.js to Go

#5

Post by drikerf » Thu, Jan 29, 2015, 8:59 PM UTC

voidlogic wrote: post #4

drikerf wrote: post #2

Go 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.

>no mature libraries for User authentication "User authentication" can mean 1,000 different things, maybe if you clarify your use case, people can suggest solutions.

Agree, that was a bit loose. Something like Passport.js(passportjs.org).

Re: From Node.js to Go

#6

Post by tptacek » Thu, Jan 29, 2015, 9:04 PM UTC

drikerf wrote: post #2

Go 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.

It's as easy to implement authentication in Golang as it is in Rails. There are gaps in the web stack for Golang (databases are particularly painful), but this isn't one of them.

Re: From Node.js to Go

#7

Post by mrKlin » Thu, Jan 29, 2015, 9:08 PM UTC

drikerf wrote: post #2

Go 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

Re: From Node.js to Go

#8

Post by timClicks » Thu, Jan 29, 2015, 9:09 PM UTC

It's interesting the switch was prompted very few things that are JS vs Go, perhaps concurrency. The main factors were tooling related, enabling stable workflows and easy deployment.

Re: From Node.js to Go

#9

Post by eknkc » Thu, Jan 29, 2015, 9:10 PM UTC

For 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.

Re: From Node.js to Go

#10

Post by enahs-sf » Thu, Jan 29, 2015, 9:11 PM UTC

Go does lack quite a bit of the web pizzazz you'd find in rails, but I learned a lot more by writing web things in go than I did in rails because so much less of the magic is hidden away from you.