6

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

Comments
  • 3
    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
  • 1
    Cause you can’t mix it with html and css in one file.
  • 4
    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.
  • 1
    Lack of promotion and hype
  • 2
    Because in our world, screaming louder means you're "more" correct. So since "everyone" is saying that Node is godsend blah blah blah, that's what HR wants.
  • 2
    @vane

    Technically, you can, because of nice things such as "go-bindata", but you definitely don't want to.
  • 0
    Well I I think biggest reason is that you can use js simply in client side too outside of nodejs. It's more attractive language because of this to new developers who is interested web development. GO could replace Python for server side
  • 2
    Because there already exists a hundred million js devs, go requires learning a new and quite different language.
  • 0
    @kescherRant you can’t create such stupid structures like reactjs and it’s frameworks
  • 0
    NOBODY LIKES GOFERS
  • 0
    @bashleigh :O :O U TAKE THAT BACK :P
  • 0
    - 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.
  • 0
    @ninjapants ARE YOU A GOFER!?!?
  • 4
    Because real life is boring
  • 2
    Because usually, unless absolutely necessary, I don't have time to learn new languages and js works well for me.
Add Comment