5 ms·

From what I heard it was fine until Microsoft bought it and decided to bring over .net code (and people) from azure devops to replace a bunch of the pre-existin

From what I heard it was fine until Microsoft bought it and decided to bring over .net code (and people) from azure devops to replace a bunch of the pre-existing github actions stuff for some reason.

bbrree66 5y ago
What actions stuff existed before the acquisition?
tester34 5y ago
You're saying that .NET is not capable or bad when it comes to handling such a tools like building systems?
- Jenk 5y ago
  I infered that it is more about Microsoft and their management of software development than I did about it being anything technical related.
- prepend 5y ago
  I read this as more a situation where an existing architecture got stuff shoehorned in for non-technology reasons. I don’t think there’s a problem with .NET inherently. But swapping out components for new tech stacks for no user or tech reason is likely to introduce bugs and at best will negatively impact schedule. Although it would be interesting to hear any new company that chose .NET over other alternatives. I really likes how Spolsky explained why they used the MS stack [0] to build stackoverflow, among other things. [0] https://channel9.msdn.com/Blogs/Seth-Juarez/Joel-Spolsky-Talks-About-Building-Stack-Overflow-and-Values-Developers-Care-About https://channel9.msdn.com/Blogs/Seth-Juarez/Joel-Spolsky-Tal...