News for hackers. Stuff that matters.
Re:Flow vs. Typescript by Aldo_MX on Monday June 06, 2016 @12:59PM (#11848234)
> Node works fantastically on Windows.

I beg to differ

1. npm install gulp

2. try to delete the node_modules folder

3. waste time fighting windows' legacy stuff (260 max path length in almost everything: explorer, cmd, git bash, etc.)

4. come across rimraf eventually

I wouldn't describe that flow as "fantastically" unless you mean "fantastically broken".

Re:Flow vs. Typescript by Joeri on Monday June 06, 2016 @02:21PM (#11848979)
Not that it helps today, but the upcoming w10 anniversary update is going to get rid of the 260 char path length limit.

Microsoft is waking up to the fact that developers mostly aren't using microsoft dev tools anymore. Hence, docker on windows, ubuntu on windows, redesigned env vars dialog, no more path length limit, nicer command prompt, etc...

Re:Flow vs. Typescript by livus on Monday June 06, 2016 @04:16PM (#11849948)
Finally. But I wish microsoft would've done it sooner. Now a UNIX convert. Forever a convert. I'm no longer fighting my system to get shit done.
Re:Flow vs. Typescript by skrebbel on Monday June 06, 2016 @02:36PM (#11849110)
Cool! About time.
Re:Flow vs. Typescript by skrebbel on Monday June 06, 2016 @02:23PM (#11848999)
Wow, that one is new to me. I just deleted a 120 MB node_modules directory by pressing "shift+del" in explorer. It went away.

I wonder what went wrong in your case.

I do remember having trouble committing a node_modules to git because of the same MAX_PATH bullshit, but then we realized that you're not really supposed to do that anyway.

More generally, by the way, NPM 3 fixed the MAX_PATH problem for the majority of cases, when they moved away from super deeply nested file trees.