7 ms·
I'd consider Windows more readily, but you are a bit screwed if you do decide you want to dip in the Open Source pool. You can dip there, but it's harder and le
by maxhowell 13y ago
I'd consider Windows more readily, but you are a bit screwed if you do decide you want to dip in the Open Source pool. You can dip there, but it's harder and less well supported, and some things simply don't work. So you are tying yourself to Windows, and often, Microsoft tools. Fine if you're sure it'll work, but I would feel like I was gambling.
- statictype 13y agoWe're building a web-based saas on a Microsoft stack. We use coffeescript, sass, compass in our development environment and it works really well. There are open source libraries for doing REST, unit testing, performance testing and they work pretty well. Node.js and npm run on Windows. Mercurial always has and git now works as well. What are the components that you miss?
- bayesianhorse 13y agoIt does sound a bit as if you were using a node.js stack on top of a Windows operating system, which I wouldn't exactly call a Microsoft stack. In which case there is really just the question of what you know better, linux ecosystem or Microsoft...
- statictype 13y agoNo, we're are using a Microsoft stack - ASP.NET MVC and Sql Server. We're not actually using Node.js in that sense. I was just pointing out that it works well (we use Node and npm to run the coffeescript compiler - that's it)