Why closed source sucks

#1

Post by jorgem » Wed, Dec 03, 2014, 10:25 PM UTC

Re: Why closed source sucks

#2

Post by LarryMade2 » Wed, Dec 03, 2014, 10:43 PM UTC

All I can say is get used to it.

Sometimes even in open source support just ends; unless you know how to patch bugs/fix dependency drift then you may be SOL there too.

Only best defence is know what your project's dependencies are and mitigate for potential loss/change.

Re: Why closed source sucks

#3

Post by dllthomas » Wed, Dec 03, 2014, 11:12 PM UTC

LarryMade2 wrote: post #2

All I can say is get used to it. Sometimes even in open source support just ends; unless you know how to patch bugs/fix dependency drift then you may be SOL there too. Only best defence is know what your project's dependencies are and mitigate for potential loss/change.

"unless you know how to patch bugs/fix dependency drift"

Or are willing to pay someone who does...

Re: Why closed source sucks

#4

Post by informatimago » Thu, Dec 04, 2014, 1:44 PM UTC

dllthomas wrote: post #3

LarryMade2 wrote: post #2

All I can say is get used to it. Sometimes even in open source support just ends; unless you know how to patch bugs/fix dependency drift then you may be SOL there too. Only best defence is know what your project's dependencies are and mitigate for potential loss/change.

"unless you know how to patch bugs/fix dependency drift" Or are willing to pay someone who does...

Whouah! You mean I COULD patch bugs, fix dependency drift or have somebody do it for me against (reasonable) payment at all? That's wonderfull!

Try to do that with Microsoft Windows or Microsoft Word!