3 ms·

This reads like a classic slashdot post to be honest. Every large enterprise I've worked at in the last say 10 years, has software deployed across multiple dev

by skc 7y ago

This reads like a classic slashdot post to be honest. Every large enterprise I've worked at in the last say 10 years, has software deployed across multiple dev stacks, with .Net being just one. This very moment consulting at a large insurance firm I'm firmly entrenched in .Net as well as React and Python. What you described may have been true in the distant past but you might need to update your views.

dustinmoris 7y ago
What do you mean by classic slashdot post? So if I am the only one who mentions a problem then it is well grounded and valid criticism, but if I am one of many developers who raises attention to the same problem then the issue loses credibility? Your experience from already 10 years ago is truly remarkable. Given that before .NET Core you were tied to IIS, and therefore tied to Windows Server and also tied to Visual Studio and for that reason also tied to Windows as a development machine, and therefore automatically limited to what other software you could smoothly run in order to connect to databases and other technology it really surprises me that 10 years ago you were developing .NET in a complete non MS tech stack.
- oblio 7y ago
  > Every large enterprise I've worked at in the last say 10 years, has software deployed across multiple dev stacks, with .Net being just one. Re-read his comment. And be less angry. He wasn't saying that he worked on cross-platform .NET projects 10 years ago, just that big companies generally had/still have .NET projects, besides other tech stacks.
  - dustinmoris 7y ago
    Are you possibly angry? Honestly, I feel very relaxed right now and I wish I could post a photo here to reassure you that I'm anything but angry :) Anyways, my initial point was that .NET folks are less likely to look outside the MS bubble when making technology choices. The other commentator said that he/she worked at large enterprises which had .NET teams and other development teams employed. That is great, but I don't see how that is relevant to my initial comment, because the question still stands if those .NET teams within those large organisations worked mostly within the MS stack or not. My second comment was aimed at suggesting that I think it must have been the latter, given that before .NET Core many tech choices were forced upon those developers due to .NET being very tightly coupled to MS technologies. So I take your point that large organisations might have many different dev teams, but that doesn't really say much about my point, which I still think can be true at the same time.

by skc 7y ago

dustinmoris 7y ago

What do you mean by classic slashdot post? So if I am the only one who mentions a problem then it is well grounded and valid criticism, but if I am one of many developers who raises attention to the same problem then the issue loses credibility? Your experience from already 10 years ago is truly remarkable. Given that before .NET Core you were tied to IIS, and therefore tied to Windows Server and also tied to Visual Studio and for that reason also tied to Windows as a development machine, and therefore automatically limited to what other software you could smoothly run in order to connect to databases and other technology it really surprises me that 10 years ago you were developing .NET in a complete non MS tech stack.

oblio 7y ago
> Every large enterprise I've worked at in the last say 10 years, has software deployed across multiple dev stacks, with .Net being just one. Re-read his comment. And be less angry. He wasn't saying that he worked on cross-platform .NET projects 10 years ago, just that big companies generally had/still have .NET projects, besides other tech stacks.
- dustinmoris 7y ago
  Are you possibly angry? Honestly, I feel very relaxed right now and I wish I could post a photo here to reassure you that I'm anything but angry :) Anyways, my initial point was that .NET folks are less likely to look outside the MS bubble when making technology choices. The other commentator said that he/she worked at large enterprises which had .NET teams and other development teams employed. That is great, but I don't see how that is relevant to my initial comment, because the question still stands if those .NET teams within those large organisations worked mostly within the MS stack or not. My second comment was aimed at suggesting that I think it must have been the latter, given that before .NET Core many tech choices were forced upon those developers due to .NET being very tightly coupled to MS technologies. So I take your point that large organisations might have many different dev teams, but that doesn't really say much about my point, which I still think can be true at the same time.