But you still have a chance with open source because the source is available. With closed source, if the company decided to not continue the product or not fix a bug, then that's the end of it.
Another advantage is the licensing. Most open source comes with generic open source licensing that everyone understands. With closed source, unless you have a lawyer, you have no chance in understanding the full extent of what you agreeing when you use the product. This is a big deal for small to medium companies. Open source with premium support is the way to go, because you get the best of both worlds. You get open source product, and you get commercial support. On Sun, Jan 10, 2010 at 1:14 AM, Lee Bolding <l...@leesbian.net> wrote: > > On 9 Jan 2010, at 03:32, Parijat Kalia wrote: > >> I like the DIY for a bug in open source vs a dead end to a bug in closed >> source as a really solid example. > > Can you give a more concrete example? yes, theoretically that's correct - but > in the PHP world, code isn't compiled. > > If you've paid for custom development, you should also receive the source > code for anything that is compiled. > > How many of you would have the ability to fix a Linux kernel bug if you found > one? > > How many people saw the critical bugs with PHP 5.2.7, and rather than fix > them themselves, waited for the next release? > > Yes, these bug fixes can be made - but just because the source is available, > that doesn't mean you have the ability to, or will pay for somebody else to > fix them. > > Have we seen any bugfixes to PHP4 after PHP 4.4.9? > > Your point is valid, but only under certain circumstances - only where the > end result is a compiled product, and the source is not available. And it's > only then ratified when you also have the ability to fix the bug - if you > don't, it makes no difference as to the availability of the source. > > > > > -- > You received this message because you are subscribed to the Google Groups > "symfony users" group. > To post to this group, send email to symfony-us...@googlegroups.com. > To unsubscribe from this group, send email to > symfony-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/symfony-users?hl=en. > > > > -- Blue Horn Ltd - System Development http://bluehorn.co.nz
-- You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-us...@googlegroups.com. To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en.
