Why didn't Golang destroy NodeJs!? Let me hear it.

Because:

- Go compiles to native binaries
- Its package handling can be garbage at times (recursively getting all needed packages for importing is a real pain when it won't work right)
- It's very restrictive

Cause you can’t mix it with html and css in one file.

It doesn't let corporate decision-makers feel like they can hire the same skill set for everything (front end, back end, etc.) like Node does.

Lack of promotion and hype

@vane

Technically, you can, because of nice things such as "go-bindata", but you definitely don't want to.

Because there already exists a hundred million js devs, go requires learning a new and quite different language.

@kescherRant you can’t create such stupid structures like reactjs and it’s frameworks

NOBODY LIKES GOFERS

@bashleigh :O :O U TAKE THAT BACK :P

- Because the way Go handles packages is absolutely garbage.
- It compiles to binaries.
- They don't even have the same goals.
- Go is much harder to learn.

Go can be a good option for many things, don't get me wrong. I do like it, but Node will remain in the number one spot for anything web related.

@ninjapants ARE YOU A GOFER!?!?

Because real life is boring

Because usually, unless absolutely necessary, I don't have time to learn new languages and js works well for me.