Why I Won't Switch To Go from Node.js • Hacker News Board

Re: Why I Won't Switch To Go from Node.js

#11

Post by klibertp » Fri, Mar 28, 2014, 7:15 AM UTC

sseveran wrote: post #2

javascript is not perfectly readable. For all the same reasons that other languages with poorly integrated async features are. Ahem C#, etc...

From the article: "Promises, 'nuff said."

There are two schools of thought here. One says that concurrent programming is actually an optimization and that the language and frameworks should make it as transparent as possible. The other says that concurrent programming is fundamentally different from sequential programming and it should look differently, too.

Out of curiosity, which language you think gets concurrency right? My personal favourites are Erlang, Io and Clojure, but even there concurrency is not completely transparent.

Re: Why I Won't Switch To Go from Node.js

#12

Post by noname123 » Fri, Mar 28, 2014, 7:16 AM UTC

I love Java and I use GWT so I avoid context switching to Javascript and plus it came out of Google like Go, so it's pretty rad.

Re: Why I Won't Switch To Go from Node.js

#13

Post by klibertp » Fri, Mar 28, 2014, 7:22 AM UTC

couchand wrote: post #8

The first three complaints addressed are far too common for how ridiculous and unfounded they are, and it's nice to see them addressed head-on. The fourth is simply confusing. If you're not sharing code between the client and the server, you're missing something big (though he does say it might just be the projects he's on). Modern business software is faced with two competing forces: bulletproof integrity and respon…

What about Clojure and ClojureScript? There's also Opa. And Ur/Web, which reached a stable state, based on a growing user base of three use cases ;)

Then there are Seaside inspired frameworks, which generate client JS for the user. There is at least one framework like this for Python and I'm sure there are other for other languages.

JS remains the most well known and supported solution, though.

Re: Why I Won't Switch To Go from Node.js

#14

Post by samnardoni » Fri, Mar 28, 2014, 11:23 AM UTC

Honest question. Why do people write posts like these?

Re: Why I Won't Switch To Go from Node.js

#15

Post by NateDad » Fri, Mar 28, 2014, 11:28 AM UTC

I'm curious as to what toolchain he thinks he needs? I write Go all day. I don't have a "toolchain" unless you count version control and go build/go get.

Re: Why I Won't Switch To Go from Node.js

#16

Post by billrobertson42 » Fri, Mar 28, 2014, 1:22 PM UTC

DigitalSea wrote: post #10

As a web developer the number #1 argument I use against those who say, why not a language like Go or Ruby is simple: I use Javascript on the front-end, why not the backend as well? Being able to handle everything from authentication to view rendering using the one language is a powerful thing. As for the last paragraph in the article, Go in my opinion is already pretty popular. It might not be mainstream like Node.js…

Everything is a nail.

Re: Why I Won't Switch To Go from Node.js

#17

Post by notduncansmith » Sun, Mar 30, 2014, 10:29 PM UTC

samnardoni wrote: post #14

Honest question. Why do people write posts like these?

Author here. I originally wrote this as a comment in a Reddit thread, and decided to put it on my blog because I felt like having more than one post (might actually start blogging regularly again).

Re: Why I Won't Switch To Go from Node.js

#18

Post by notduncansmith » Mon, Mar 31, 2014, 2:16 AM UTC

lugg wrote: post #9

mathrawka wrote: post #5

Honestly, does a context switch exist for switching between frontend JS and backend Go? I am not trying to tout my own horn here, but I don't have problems with that. And this is coming from someone who has used Node.js for multiple startups in the past 2.5 years.

I believe the author meant between frameworks, patterns and compilation styles. To a lesser extent syntax (that's probably the most visible but least painful). To be honest, I'm not sure what that point was about I still feel a context switch going from server side node js in my apis and apps to client side angular / backbone. They are just different beasts. Unless he does a lot of the node in the browser thing? I do…

Author here.

> I believe the author meant between frameworks, patterns and compilation styles. To a lesser extent syntax (that's probably the most visible but least painful).

Spot on.

> To be honest, I'm not sure what that point was about I still feel a context switch going from server side node js in my apis and apps to client side angular / backbone.

That's not a point I was trying to make, perhaps I wasn't clear. The context-switching I was talking about wanting to avoid was Go (or some other language) and Javascript, and the fact that my tooling is JS means I'm gonna be switching all the more often. I don't really have a problem switching between client and server-side JS.

In fact, context-switching isn't that hard for me, but being able to avoid it is a nice bonus that comes with what happens to be my favorite stack.

Re: Why I Won't Switch To Go from Node.js

#19

Post by notduncansmith » Mon, Mar 31, 2014, 3:50 AM UTC

NateDad wrote: post #15

I'm curious as to what toolchain he thinks he needs? I write Go all day. I don't have a "toolchain" unless you count version control and go build/go get.

As a full-stack web developer, I rely heavily on gulp and Bower (as mentioned in the article), as well as a few other small utilities. I know I wouldn't have to give those up by switching to Go, but at that point, if every dev on the project already needs to have Node installed, why not just use Node?