3 ms·
I was suprised to see the comment that tooling for Node wasn't great; I thought the node tooling (npm, gulp, grunt, etc.) was significantly superior to the prim
by shadowmint 12y ago
I was suprised to see the comment that tooling for Node wasn't great; I thought the node tooling (npm, gulp, grunt, etc.) was significantly superior to the primitive (ie. relatively low level) tooling go provides.
...but I see that's a very specific comment:
the tooling Go provides for profiling and debugging is great...
Ah, that makes more sense. This is definitely an area where node applications are really troublesome to work with (live debugging).
- notduncansmith 12y agoI was surprised as well, until I saw that. The npm/gulp/bower/less/node stack is pretty awesome for full-stack web development. All in one language, all open source, easy-breezy package management. If Go had that sort of complete stack (and for God's sake a package manager to rival npm), I'd probably be pushing Go as hard as possible at work. As it stands, there's way too much friction and it would cost a LOT of money to invest in Go. There's a good chance that the ecosystem may not evolve to Node's level for years - and worst of all, if you want to build competitive web apps, you still can't avoid Javascript.