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.
