←back to thread

Ubuntu on Windows

(blog.dustinkirkland.com)
2049 points bpierre | 1 comments | | HN request time: 0s | source
Show context
matt_wulfeck ◴[] No.11391211[source]
microsoft is leveraging FOSS Linux to get Mac users. I think it's a real smart move.

The author points to using grep and Xargs and some other tools to quickly update a package. That's the key here. These bash/Linux utilities are productivy boosters for all the Linux and Mac/bsd people out there. I can't imagine living without them and they're necessary for any system I develop on (which is currently a Mac).

replies(6): >>11391411 #>>11391451 #>>11391515 #>>11392124 #>>11392170 #>>11393505 #
simonlc ◴[] No.11391411[source]
I completely agree. I only really switched to OSX because getting node tools to work on windows and cygwin is a pita.
replies(2): >>11391709 #>>11392450 #
skrebbel ◴[] No.11392450[source]
Wait, getting node to work on windows is a pita?

I know of no language runtime and ecosystem that has better cross-platform support than Node (hm ok maybe Java also). I develop solely on Windows (I just like it better) and virtually all of NPM just works on my box. Even stuff people never tested elsewhere than on their Macs, it just works. Express, webpack, mocha, phantomjs, it's really quite impressive if you ask me.

replies(3): >>11392664 #>>11393515 #>>11394316 #
itsananderson ◴[] No.11392664[source]
99% of the painful Node stuff on Windows comes down to native packages. To even compile, you have to install Visual Studio. Then you have to hope the module developer has a build definition that even works for Windows.
replies(1): >>11395824 #
1. edwinyzh ◴[] No.11395824[source]
Correct! The last time I wanted to npm-install a CLI but it needs gyp, I'm not familiar with the node thingy and I gave up after several failed attemps including installing the VC++ runtime, Python, etc....