Re: GNU Public Licences Revisited (again)

Perhaps you could give an example of a closed source application that "makes
it a lot more difficult to switch [to another] vendor [compared to the open
source version]"

I have no experience of this, but imagine, for a typical business with no
in-house software engineers, that the total cost of dealing with a major
problem due to a less-than-ideal closed-source vendor would not be
significantly different than dealing with a similar problem in an
open-source alternative (particularly one that required the sourcing of
3rd-party support).

If you get software from a closed source vendor that becomes problematic,
you probably still have the option of moving to another system. There are
likely to be very few systems where a transfer of data is impossible. If,
instead, you are using an open source system that becomes a major problem,
you are now reliant on the 'community' still being around and giving your
problem a high priority on the fix list. If the project is dormant, you've
now got the problem of finding a developer that can fix the problem (at a
cost - that's one of the OSS 'community' dogmas, remember) - perhaps the
company with the problem don't have the source to the version they are
using, perhaps they've already had some mods made that are now lost, not
spec'd out and would need to be re-implemented if the baseline source could
even be located via some Internet archive.

"Willem" <willem@xxxxxxxx> wrote in message
news:slrndj8hvp.2il2.willem@xxxxxxxxxxxxxxxx
> Joe wrote:
> ) No, you loose if you were dumb enough to pick such a product when it
didn't
> ) fulfill all of your needs from the outset - particularly if there were
> ) alternatives. This would be the case if you choose open source or
closed
> ) source - remember that the vast majority of sotware users have no idea
how
> ) to program (or even how to use a product to its full potential).
>
> This comparison lacks, because in the case of open source, you can find
> another company willing to support the OSS you bought from one company.
>
> In the case of closed source, the only company able to give you support
> is the company you bought the CSS from in the first place, and if that
> company turns out to be bad in whatever way, you're screwed.
>
>
> SaSW, Willem
> --
> Disclaimer: I am in no way responsible for any of the statements
> made in the above text. For all I know I might be
> drugged or something..
> No I'm not paranoid. You all think I'm paranoid, don't you !
> #EOT


.

Relevant Pages

  • Re: What so special about PostgreSQL and other RDBMS?
    ... > Free, loaded with features, not particularly fast, some extras ... choice between closed and open source really means, ... backer, and with closed source, you can only chose the copyright ... Since you have no source code, no one knows but Microsoft (and the ...
    (comp.lang.php)
  • Re: [Full-Disclosure] why commcerical software *could* be better [WAS: Re: [Full-Disclosure] Microso
    ... I did a presentation on open vs. closed source security at ... the Open Source Security Summit. ... My theory is that since format string bugs and symlinks were found ... this notion is to look at PROTOS-style vulnerability testing suites ...
    (Full-Disclosure)
  • Re: Qns on linux security frm windows users :::Help !!!
    ... But can anyone help me with some qns which windows users asked me...??? ... If you are getting your versions of Open Source software ... The alternate case is that some programmer makes Bar Deluxe as a closed ... a closed source software project is likely to have sloppy ...
    (comp.os.linux.security)
  • Re: Whats the story with the "end of XP"?
    ... one case it was being actively promoted by the FOSS Devotees over the commercial SW simply because it was FOSS for all the usual reasons... ... There are times when being open source is an absolute requirement, and poor open source software is then infinitely better than wonderful closed source software. ...
    (comp.arch.embedded)
  • Re: Whats the story with the "end of XP"?
    ... You can't call yourself an expert in cryptography without a solid familiarity with some of the most used algorithms and implementations - programs like GPG, OpenSSH and OpenSSL are known to be among the most secure solutions precisely because there are so many interested and capable people who have studied their source code. ... There is overwhelming statistical evidence that serious flaws in major open source software projects are fixed quickly - generally far faster than in comparable closed source projects. ... And there are people who feel that anyone can use whatever license they want, but that they personally will only use FOSS. ...
    (comp.arch.embedded)