News for hackers. Stuff that matters.
Re:From Node.js to Go by eknkc on Thursday January 29, 2015 @04:10PM (#8968852)
For me the single biggest disadvantage of Go against Node.JS is the lack of a decent dependency management solution. NPM is awesome and Go doesn't even have a "meh" answer to that.
Re:From Node.js to Go by bacongobbler on Thursday January 29, 2015 @04:21PM (#8968910)
I feel and share your pain. I dislike the model of having to vendor in every third party library's source code, so I'm trying to build an alternative tool to Godep[1]. It's still a work in progress but the basic functionality is there :)

[1]: https://github.com/fishworks/dis

Re:From Node.js to Go by frakkingcylons on Thursday January 29, 2015 @04:16PM (#8968880)
What problems have you had managing dependencies with Go? I use Godep to vendor each dependency and rewrite import paths to use the vendored package. I found it to be an easy and effective solution.
Re:From Node.js to Go by mcmillion on Thursday January 29, 2015 @04:37PM (#8969003)
NPM is only awesome until you need to do something with it on Windows.
Re:From Node.js to Go by u84six on Thursday January 29, 2015 @05:16PM (#8969233)
What kind of problems are you having with it? I'm using npm on Windows and it's working out great! I'm actually using it as my build/task runner rather than using bloated grunt or gulp. It's easy to configure and read. I run my linter, unit test, jscs, and bundler all configured in package.json.

I also install git bash and conemu to have bash on Windows which makes things much better. I don't use windows console.

Re:From Node.js to Go by nawitus on Thursday January 29, 2015 @05:34PM (#8969338)
My experience is that Npm "kinda works" on Windows. There are mysterious race-conditions and annoying bugs. And I'm not even talking about npm being technically completely incompatible with Windows due to the 256 character path limitation.
Re:From Node.js to Go by cozuya on Thursday January 29, 2015 @09:15PM (#8970131)
I had a global environment variable conflict because something else was named "node.exe"... =/
Re:From Node.js to Go by britknight on Thursday January 29, 2015 @09:37PM (#8970180)
It's not just npm. A while back I had to set up a Rails dev environment for a client who used Windows. shudder.
Re:From Node.js to Go by pjmlp on Thursday January 29, 2015 @04:59PM (#8969137)
Never had any problem with it when we did a Cordova based application for a customer of ours.
Re:From Node.js to Go by kybernetikos on Thursday January 29, 2015 @05:21PM (#8969256)
There are quite a few packages in npm that require native compilation of some part of their system during install. These usually fail horribly on windows without spending a lot of time tweaking your system in ways you probably don't want to. This is in sad contrast to how well many of the other libraries just work.

I would have thought it'd be possible to emscripten compile something like tinyC, and make a C compiler you could naturally fit into the node ecosystem to build native libraries.

Re:From Node.js to Go by pjmlp on Friday January 30, 2015 @03:52AM (#8971104)
I see. However that is a common problem in any platform that doesn't follow the UNIX way.

I imagine node.js for IBM i or z/OS to have similar issues.

Re:From Node.js to Go by kybernetikos on Saturday January 31, 2015 @03:22PM (#8977959)
This is almost certainly true, and if there were as many people trying to use node on those operating systems as there are on windows I expect you would see a similar number of complaints.
Re:From Node.js to Go by xasos on Thursday January 29, 2015 @05:00PM (#8969144)
Maybe it's just me, but I really like the way Go does package management. Not needing to publish to a central place for packaging is awesome (just have it on any website), but I agree that it needs reorganization (godep is a step in the right direction)