4 ms·

To be fair you are not immune from this by using OS projects. I have made extensive use of projects in the past that have had active repos and mailing lists on

by jiggy2011 14y ago

To be fair you are not immune from this by using OS projects. I have made extensive use of projects in the past that have had active repos and mailing lists only to have them slowly turn into a ghost town because one of the major maintainers stopped working on it and nobody else stepped in.

meaty 14y ago
At least you can fork it internally though and support it if need be. The same is not the case with something like XNA which is so tied into the OS that when they drop it, you're up shit creek.
- jiggy2011 14y ago
  True, thought it is important to be realistic about your ability in terms of time/skills to do so. For OSS I like for one of three things. Either "too big to fail" (i.e Linux , Rails). Interchangeability , i.e something built on top of an open protocol like an SMTP server. Or something with < ~10KLOC in language I am familiar enough with that I would feel comfortable folding the entire thing into the codebase as a whitebox.
- pretoriusB 14y ago
  >At least you can fork it internally though and support it if need be. That's almost as realistic as "the community could do a clean-house implementation of XNA" for large projects. That you wanted to use an project in your work, doesn't mean you could also maintain it when it's abandoned. You might not have the: interest, motivation, time, skills.
- cobrausn 14y ago
  pretoriusB, you appear to be hellbanned. Not quite sure why - I don't see anything offensive in your comment history.
  - jiggy2011 14y ago
    Quite a few of his comments have a slightly antagonistic tone but I don't see anything in his recent history that would obviously justify a hellban.
- daeken 14y ago
  > The same is not the case with something like XNA which is so tied into the OS that when they drop it, you're up shit creek. While you can't fork XNA and support it, it's not even remotely tied to the OS. It's a content pipeline and a thin wrapper around DirectX's various components. There's really nothing magical there, and certainly no low-level pieces.
  - meaty 14y ago
    Try shipping it with your product in about 5 years...
  - yxhuvud 14y ago
    Uh, how exactly is DirectX not tied to the OS?
    - daeken 14y ago
      XNA != DirectX. XNA is a very thin wrapper over DX, but it's not tied into the OS itself by any means.
chaostheory 14y ago
Yes but you and a lot of other people have the source. Moreover you and a lot of other people can fork the project. At the very least, there will be bug fixes on going. That makes a huge difference.

meaty 14y ago

At least you can fork it internally though and support it if need be. The same is not the case with something like XNA which is so tied into the OS that when they drop it, you're up shit creek.

jiggy2011 14y ago
True, thought it is important to be realistic about your ability in terms of time/skills to do so. For OSS I like for one of three things. Either "too big to fail" (i.e Linux , Rails). Interchangeability , i.e something built on top of an open protocol like an SMTP server. Or something with < ~10KLOC in language I am familiar enough with that I would feel comfortable folding the entire thing into the codebase as a whitebox.
pretoriusB 14y ago
>At least you can fork it internally though and support it if need be. That's almost as realistic as "the community could do a clean-house implementation of XNA" for large projects. That you wanted to use an project in your work, doesn't mean you could also maintain it when it's abandoned. You might not have the: interest, motivation, time, skills.
cobrausn 14y ago
pretoriusB, you appear to be hellbanned. Not quite sure why - I don't see anything offensive in your comment history.
- jiggy2011 14y ago
  Quite a few of his comments have a slightly antagonistic tone but I don't see anything in his recent history that would obviously justify a hellban.
daeken 14y ago
> The same is not the case with something like XNA which is so tied into the OS that when they drop it, you're up shit creek. While you can't fork XNA and support it, it's not even remotely tied to the OS. It's a content pipeline and a thin wrapper around DirectX's various components. There's really nothing magical there, and certainly no low-level pieces.
- meaty 14y ago
  Try shipping it with your product in about 5 years...
- yxhuvud 14y ago
  Uh, how exactly is DirectX not tied to the OS?
  - daeken 14y ago
    XNA != DirectX. XNA is a very thin wrapper over DX, but it's not tied into the OS itself by any means.

chaostheory 14y ago

Yes but you and a lot of other people have the source. Moreover you and a lot of other people can fork the project. At the very least, there will be bug fixes on going. That makes a huge difference.