4 ms·

Closed source. If it breaks (really breaks) I (or anyone without a Microsoft badge) can't fix it. And if they do fix it, it will take a while for the patch to g

by gfodor 16y ago

Closed source. If it breaks (really breaks) I (or anyone without a Microsoft badge) can't fix it. And if they do fix it, it will take a while for the patch to get to me. Pretty simple if you ask me.

chrisjsmith 16y ago
Ironically, I spend at least 25% of the time when working with .Net fixing stuff that has broken.
MichaelGG 16y ago
Well, the number of engineers that can actually patch something, in say, the JVM, are rather limited. So I'm not sure open source is nearly as big a deal as it's made out to be, as far as patching goes. You do have a point on release cycles, but that's not inherently about being closed source.
- bxr 16y ago
  >Well, the number of engineers that can actually patch something, in say, the JVM, are rather limited. So I'm not sure open source is nearly as big a deal as it's made out to be, as far as patching goes. Rather limited? Thats just not a good excuse where I'm coming from. If I need a bug fixed, it doesn't matter I don't know jack about the JVM today, if the cheapest way for me to fix the bug is to jump in myself, I'm going to become a member of that very limited group that can patch the JVM. It would be nice if we were developing in an environment that we could throw our hands up and walk away, but in the project I'm working on, we've already had to dig very deep into opensource components of our stack to fix their bugs that would have blocked us from shipping.
- deleted 16y ago
  [deleted]
- gfodor 16y ago
  This argument is broken because the open source-ness of the ecosystem bleeds all the way up the stack. In Java, you get the source of the JVM, of course, but also the Java frameworks and, generally speaking, most Java projects out there are open source. On the .NET side, which is a closed source culture, you'll not be able to fix issues with the core framework nor the array of other closed source, commercial frameworks that exist due to this cultural difference.
mmcconnell1618 16y ago
Actually, the full source of the ASP.NET stack is now available from Microsoft and you can easily get decompiled source from .NET framework classes. I would agree that fixing a bug (if found) would be difficult but at least you could understand the behavior and code a work around or substitute.

by gfodor 16y ago

Closed source. If it breaks (really breaks) I (or anyone without a Microsoft badge) can't fix it. And if they do fix it, it will take a while for the patch to get to me. Pretty simple if you ask me.

chrisjsmith 16y ago

Ironically, I spend at least 25% of the time when working with .Net fixing stuff that has broken.

MichaelGG 16y ago

Well, the number of engineers that can actually patch something, in say, the JVM, are rather limited. So I'm not sure open source is nearly as big a deal as it's made out to be, as far as patching goes. You do have a point on release cycles, but that's not inherently about being closed source.

bxr 16y ago
>Well, the number of engineers that can actually patch something, in say, the JVM, are rather limited. So I'm not sure open source is nearly as big a deal as it's made out to be, as far as patching goes. Rather limited? Thats just not a good excuse where I'm coming from. If I need a bug fixed, it doesn't matter I don't know jack about the JVM today, if the cheapest way for me to fix the bug is to jump in myself, I'm going to become a member of that very limited group that can patch the JVM. It would be nice if we were developing in an environment that we could throw our hands up and walk away, but in the project I'm working on, we've already had to dig very deep into opensource components of our stack to fix their bugs that would have blocked us from shipping.
deleted 16y ago
[deleted]
gfodor 16y ago
This argument is broken because the open source-ness of the ecosystem bleeds all the way up the stack. In Java, you get the source of the JVM, of course, but also the Java frameworks and, generally speaking, most Java projects out there are open source. On the .NET side, which is a closed source culture, you'll not be able to fix issues with the core framework nor the array of other closed source, commercial frameworks that exist due to this cultural difference.

mmcconnell1618 16y ago

Actually, the full source of the ASP.NET stack is now available from Microsoft and you can easily get decompiled source from .NET framework classes. I would agree that fixing a bug (if found) would be difficult but at least you could understand the behavior and code a work around or substitute.