[Udo]

This sums up the problem:

> Not looking at Go yet? It may be a good time to do so now — everybody else is.

That's going to be a large albatross around Go's neck, as it has been around node.js', and Rails before that. Large amounts of developers flocking to a new thing because "this is the thing to use now and if you don't you're dead meat".

Personally, I thought Node.js was a terrible platform for serving dynamic web sites. It is, however, a great platform if you need to make a reasonably performant general server with minimal effort (such as a message broker for example).

Likewise, people will now order their projects in Go whether it makes sense given the requirements or not. 20 years of Go experience will be needed on CVs. And when Go inevitably fails at certain things, "everybody" will move to the next thing - probably Rust, thereby completing the migration away from dynamic scripting.

This is not reasonable, is it?

[aikah]

> That's going to be a large albatross around Go's neck, as it has been around node.js', and Rails before that. Large amounts of developers flocking to a new thing because "this is the thing to use now and if you don't you're dead meat".

TJ's blog post is basically like if DHH ditched Ruby/Rails for Go.

> Personally, I thought Node.js was a terrible platform for serving dynamic web sites. It is, however, a great platform if you need to make a reasonably performant general server with minimal effort (such as a message broker for example).

Totally agree with you,nodejs is not a silver bullet.

[collypops]

It's more like Zed Shaw leaving Ruby for Python.

That happened. So did lots of other stuff. Same as it always was.

[adamors]

> "this is the thing to use now and if you don't you're dead meat".

And not just because you'd be unfashionable, but because a lot of crucial libraries in these ecosystems will loose maintainers. The Node guy said the other day that (out of his hundreds of libraries) "Koa is the one project I’ll continue to maintain".

If I had any of his packages in production I would be terrified. The fact that he (and other "Node guys") are driving the hype train to Go tells me that I should stay as far from it as possible.

[Udo]

True, I think you're expected to follow the cool people to wherever they go next ;)

Maybe some ecosystems are much more about the people leading them than they are about the technology behind them. And while this is not something I'd be interested in as a developer, I understand how there could be huge benefits in that kind of lifestyle. I imagine that's a very supportive, creative, and active community to be in.

Looking at some (mis-)uses of Node, maybe that's been the rationale behind some of these frameworks all along. And indeed the first image on the page is of a marching band...

[rdtsc]

> Large amounts of developers flocking to a new thing because "this is the thing to use now and if you don't you're dead meat".

Well "why did you pick this technology?" question is a good way to find out who are you talking to. If they say "webscale" and "callbacks are this new concurrency paradigm" then well, I might not form the best opinion about them.

[binocarlos]

It's like everyone looking at everyone else's fashion sense and then quickly getting down the shops to buy up the same sort of stuff.

I suppose it depends on what you are trying to do - if it is looking good to those with fashion sense - better get down them shops. If it's to like, actually build stuff - the feeling of being uncool because of what language you use is a massive distraction to ignore.

I've been learning Go because its a great language for concurrent server systems (and better than node in some areas).

That I feel slightly cooler because of that choice feels a bit like having the right daps (sneakers) at school.