5 ms·
The main problem for me, is that Flow doesn't support Windows (yet?). I've been working solo on a frontend a couple of months now, and the team has just been ex
by Skinney 10y ago
The main problem for me, is that Flow doesn't support Windows (yet?). I've been working solo on a frontend a couple of months now, and the team has just been extended with a new developer (yay). However, he uses Windows, and so all my type annotations are worthless. We're making the switch to TypeScript once 2.0 is released (easier to port with strictNullChecks).
- deleted 10y ago[deleted]
- spicyj 10y agoWindows support is coming soon; the Flow team is actively working on it -- so hopefully you'll see something in a few weeks.
- Bakesteve 10y agothats great. Though I would add in the flow vs TS debate the level of community suport / openness is (currently) hugely in typescripts favour, and for a tool that you are going to embed inot a lot of your files, so a reasonable effort to unwind, that matters. If you compare: https://github.com/Microsoft/TypeScript/milestones https://github.com/Microsoft/TypeScript/milestones and https://github.com/Microsoft/TypeScript/wiki/Roadmap https://github.com/Microsoft/TypeScript/wiki/Roadmap to the lack of information on progress from the flow team, especially on the win support issue https://github.com/facebook/flow/issues/6 https://github.com/facebook/flow/issues/6
- coke12 10y agoOff topic, but what's the current status of flow-replacing-PropTypes?
- greenspot 10y agoReally wondering: who is developing Node/JS on Windows nowadays? Not that I don't like Windows (I like W10 + the new Ubuntu within efforts a lot), but the ecosystem around Node is so much tailored around Linux. Even with OSX where we have an excellent support, there's still some slight friction when deploying to Ubuntu. Or is Windows 10 a viable alternative for Node devs?
- LionessLover 10y agoI do, and I'm a Unix person, even having contributed code to the Linux kernel and I've used Unix - Solaris, HP-UX, NeXTSTEP, Linux, Reliant Unix (Siemens), IRIX (SGI) since 1994. It's just that over time I fond it more and more of a -useless - hassle to keep a VM with Linux on my desktop, and pure Linux desktop never was a question (for various reasons). When I install git for windows and ConEmu64 I have a good terminal and a bash and the basic Unix command line tools. The IDE and node.js are the same anyway. I configure the IDE and git so that my projects only have one type of line endings (Unix). I have zero Windows server experience since that is all Unix for me, but on the (developer) desktop I don't feel any need for Unix.
- pingec 10y agoI develop on Windows and deploy to Linux regularly, zero problems. Most of the projects are purely js with no dependencies on binaries.
- tlrobinson 10y agoLast time I tried to do something with Node on Windows I ran into the maximum path length issue, but I guess npm 3 is supposed to help with that?
- novaleaf 10y agoCorrect, i have not seen the path issue since 3.x
- duncanawoods 10y agoYeah, I do. Workstation is W10, Laptop OSX and deploy to Linux. I don't have any problems. I have sometimes found bugs introduced into a library that only affects one platform but not the others. This has happened on things like grunt-plugins rather than more critical libraries. It hasn't caused any drama other than delaying updating a dependency until its fixed.
- aquadrop 10y agoNode.JS is actually pretty well adjusted for Windows. They made it cross-platform from the beginning and you have zero problems unless need some linux-compiled native dependencies. VS2015 is using node successfully for built-in grunt/gulp task runner.