4 ms·

With git and node it was the ease of deployment and scripting. I have done some TFS scripting which was always a total nightmare. With git it’s so easy. You can

With git and node it was the ease of deployment and scripting. I have done some TFS scripting which was always a total nightmare. With git it’s so easy. You can like npm or not but it’s pretty phenomenal how it’s set up and works. MS was way behind the curve with nuget. The more I look into Linux tools I find them way more practical than what MS has to offer. There is just more innovation. See containers too. MS is years late. Pretty much every new trend gets started on Linux these days.

JamesBarney 7y ago
Every Microsoft shop I've been in for the last 5 yrs has been git, and you're right git was leaps and bounds better than TFS. Its funny npm is one of the things I always hate. Several times a project I have to rimraf node_modules at some point due to some weird hidden state in npm. Containers are an amazing technology, but sometimes I think they make it too easy to overcomplicate a project. Been on too many projects where we solved a similar problem 4 years ago with a web app and a service and a team of 3 devs, but now the same project is a team of 8 with 4 devops guys and 7 containers. The last node project I was on was the MEAN stack. It seemed like it was pretty similar to the standard .NET apps I work on, you have an entry point, you make some database calls and you display them. Pros were the code re-use was nice, you could copy and paste your validation logic from back end to the front end. The cons were the lack of typing made it a little hard to navigate the back end, it looked like they basically reimplemented a poor man's relational database in mongo without any referential integrity, and it was harder to come up to speed without having a schema to look at and understand the domain.