[Dobbs]

I can only speak from the perspective of my company. We had quite a few pro-node people. They wrote services in node.

All of those node services have since been rewritten in Go by the formerly-pro-node people. Go has been much more manageable and powerful.

[rdtsc]

Just wait 5 years they'll be re-written in Swift, Dart, Rust (other shiny new thing). The important thing is, it will probably be the same people doing it ;-)

[Pharohbot]

Really? Dart?

[rdtsc]

Is that not cool anymore. What's the next "cool" thing?

[Pharohbot]

ITs not that its not cool, its the likelihood of Dart to be implemented in most browsers is low.

[danellis]

Browsers don't implement CoffeeScript, TypeScript, etc either, but that hasn't hindered those projects.

[Pharohbot]

Okay now I see your point, but Dart is far from replacing Node or IO as the next cool thing.

[jerf]

As I said on reddit as well, I'd really like to hear from someone with a year of serious Node experience and then a year of serious Go experience who ended up wanting to go back to Node, for anything other than perhaps a library than only Node had. While the Internet is large and any crazy criterion will match somebody, somewhere, my strong suspicion is that this is not a large set of people. I suspect it's more-or-less a one-way door.

[Kiro]

What kind of services are they?

[pearjuice]

Hello World, a todo list and a blog application. After that we put "proficient experience with node.js" on all of our developers their CVs. Our company website now lists that we have "enterprise grade expertise with Node.JS" and I haven't even talked about the nodejs-rebranding of our social media dootprint (exclusively liking, following and interacting with nodejs content). We are basically swimming in nodejs client work now. So much, that we are considering splitting the company and having an exclusive branche for the nodejs playfield.

[stephenhandley]

#dootprint