[mathrawka]

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.

[lugg]

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 dont know how you would avoid the context switch. There is, I guess, a chance the author is seeing that as an obvious but actually nonissue stemming from his other complaint (which I agree with) the tool chain.

The npm and friends tool chain is absolutely bliss to work with from a web developers point of view. While it is all doable with other more traditional build tools like ant or make there is something awesome about every part of your stack being in a single scripting language.

While right tool for the right job is still valid its amazing what has been accomplished in the ecosystem against all odds from javascripts initial debut..

[notduncansmith]

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.