It's not simply about marketing or branding. It's about accountability.
With an open-source project there is no accountability. A corporation may
use open-source software, but it will be purchased through a company that
can offer support and more importantly accountability. So when the
corporation's database gets turfed for whatever reason they have someone
they can blame - someone who will fix the problem.
Derek Vadneau
I would say that it depends on the corporation policy.
There are two possible approaches there :
a) spend a lot of money to get some support on closed source software in
the case something goes wrong.
b) use open source software and IF something goes wrong, pay someone to
fix it for you.
If nothing goes wrong, guess which one is cheaper ? :)
And if something goes wrong, then in all closed source softwares, EULA
prevent all kind of accountability anyway because software companies
don't want to get used for lost data - even if it was a bug in their
application. You'll of course get some kind of support, and hopefully
your bug will take a few weeks to get fixed, but in general when someone
ask for a bug fix in open source software, it gets fixed in a matter of
hours.
Nicolas
_______________________________________________
[email protected]
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
