News for hackers. Stuff that matters.
Re:Flat Tree Dependency Resolution in Npm v3 by ag_dubs on Thursday December 31, 2015 @12:47PM (#10818668)
hi! i totally know this is a common feel for many npmjs users. this is why i've been running an empathy campaign for Windows, Windows Wednesday, where i do all my work (with/for npm) on windows. it's been good for finding bugs, either technical or UX. i'm working on improving the docs to make them friendlier to all platforms (not just OSX, which is the most common platform at npmjs).

npmjs cares about the enterprise + windows.

Re:Flat Tree Dependency Resolution in Npm v3 by city41 on Thursday December 31, 2015 @12:59PM (#10818737)
I think this is the wrong approach. We shouldn't pick up MS's slack, MS should. This just enforces the current situation and keeps enabling MS to ignore the problem.
Re:Flat Tree Dependency Resolution in Npm v3 by ag_dubs on Thursday December 31, 2015 @06:41PM (#10820361)
you might also consider the fact that OSX machines are expensive. and the education for learning linux is generally expensive or not accessible. so supporting windows also supports ... poor people, people from different countries that have different economies, etc.

should we not pick up capitalism's slack? capitalism sure isn't going to pick up its own slack, err... systemic method of restricting underprivileged/poor people's access to power.

Re:Flat Tree Dependency Resolution in Npm v3 by fapjacks on Friday January 01, 2016 @11:28PM (#10825032)
> the education for learning linux is generally expensive or not accessible

Wow, this is incredibly wrong. The cost of education to learn Linux is living in a country where you are likely to be literate and have access to a computer. That is literally the cost to learn Linux, guy. There is nothing like an MSDN subscription for Linux documentation.

Re:Flat Tree Dependency Resolution in Npm v3 by steveklabnik on Thursday December 31, 2015 @01:37PM (#10818918)
What problem is that? That they have a different operating system?

npm is also a bit different, in your objection: they're a company. Companies need users. Supporting more platforms to get more users seems like pretty much, well, business as usual.

Re:Flat Tree Dependency Resolution in Npm v3 by city41 on Thursday December 31, 2015 @01:47PM (#10818974)
That is a fair point. npm being a company does change the situation.
Re:Flat Tree Dependency Resolution in Npm v3 by gelasio on Thursday December 31, 2015 @01:22PM (#10818848)
So, are you of the opinion that OSS projects should never be built for any commercial, proprietary OS or just Windows (i.e. because it's not Unix)?

For instance - OS X window managers suck. Do you think that a project like Spectacle should have never been built because they're just picking up Apple's slack?

Re:Flat Tree Dependency Resolution in Npm v3 by city41 on Thursday December 31, 2015 @01:36PM (#10818914)
I don't see how a project like Spectacle, which is OSX specific, relates. If someone wants to make an OS specific project, more power to them. The issue arises on platforms that span OSes, and they just never quite span onto Windows correctly.

Microsoft is very happy that Node, Java, Clojure, etc work on Windows. It helps them a lot. But they make little to no effort to help bridge the gap, they usually leave that to everyone else. That's my gripe, right there.

And to be fair, this is not a black and white situation. It's complex and Microsoft's role in all of this is complex too. And sometimes this issue does crop up on other OSes, for example Docker on OSX is sometimes a little painful.

Re:Flat Tree Dependency Resolution in Npm v3 by gelasio on Thursday December 31, 2015 @02:07PM (#10819086)
"But they make little to no effort to help bridge the gap, they usually leave that to everyone else."

OK, but that's also where you're wrong, right there. In general, but also particularly for this exact issue - Microsoft considered attempting to fix the file path limit for the first release of Windows 10. Maybe you don't understand, but it's going to take a herculean effort to fix this. They want to do it and if you need proof of that I can find posts of them talking about what I just said.

Re:Flat Tree Dependency Resolution in Npm v3 by martindevans on Thursday December 31, 2015 @03:06PM (#10819391)
Don't UNC paths solve this problem already (30000+ char limit)?
Re:Flat Tree Dependency Resolution in Npm v3 by tracker1 on Thursday December 31, 2015 @06:46PM (#10820377)
The problem is the default/legacy APIs don't use the new paths... in .Net I had this problem a lot, and serious issues every method I tried to work around it would hard crash VS, let alone the application I was working on... in the end, after days trying the solution was to say f*ck it and just put the directory I was working with closer to the root of the drive in question.

Why they can't fix .Net under the covers to use UNC in windows to avoid the class of problem I don't know, understand or comprehend... and that's just one very common platform for windows. I would say the same for npm/node and libuv for that matter.

I use bash a lot in windows (installed with msysgit), and that's got it's own set of problems. More problematic is the number of node modules that rely on bash scripts for builds, that don't work at all in windows.... which makes it very hard to contribute.

Re:Flat Tree Dependency Resolution in Npm v3 by nawitus on Thursday December 31, 2015 @03:06PM (#10819390)
I believe Microsoft worked to get Node.js supported on Windows.
Re:Flat Tree Dependency Resolution in Npm v3 by steveklabnik on Thursday December 31, 2015 @04:26PM (#10819776)
Not just that, but they're working on making Node work with Chakra.
Re:Flat Tree Dependency Resolution in Npm v3 by Touche on Thursday December 31, 2015 @04:36PM (#10819824)
Can they make it so I can spawn a process and not worry about whether I'm spawning on unix or Windows?
Re:Flat Tree Dependency Resolution in Npm v3 by steveklabnik on Saturday January 02, 2016 @01:59PM (#10827351)
I don't know it at that level of detail.