| |||||||||||||
LFCS 2012: The future of GLIBCLFCS 2012: The future of GLIBCPosted Apr 18, 2012 18:13 UTC (Wed) by aliguori (subscriber, #30636)In reply to: LFCS 2012: The future of GLIBC by pr1268 Parent article: LFCS 2012: The future of GLIBC
I think it's more about extremes. Letting anyone commit random pieces of crap to a project results in a PHP.
But having a single person declare that entire architectures are broken and therefore not worth supporting in something like glibc is going to the extreme in the other direction.
There are a lot of very experienced folks now guiding the glibc community. I think it's a wonderful thing and I expect lots of goodness to come from it. I'm looking forward to dusting off some old patches and trying again to fix a few things...
(Log in to post comments)
LFCS 2012: The future of GLIBC Posted Apr 18, 2012 18:18 UTC (Wed) by nix (subscriber, #2304) [Link]
Likewise. I've been grinning like a maniac these last couple of months whenever I think about what's happening to glibc :)
LFCS 2012: The future of GLIBC Posted Apr 20, 2012 8:44 UTC (Fri) by jzbiciak (✭ supporter ✭, #5246) [Link] I think the crucial difference here is that the progenitors of PHP themselves had severe contempt for proper design and implementation. Worse may be better, but worst is worst. Some context -- I don't believe the C library to be the best possible library beyond reproach. GLIBC inherits from the storied C / UNIX / POSIX legacy, and has to deal with all the fun that comes with that. That said, that legacy also comes with a lot of experience and respect for proper design and implementation. I don't see any radical rejection of proper software engineering practices or proper architecture happening. I think GLIBC will be just fine. PHP, on the other hand, seemed to reject such things from the get-go, if I read Rasmus' quotes properly.
LFCS 2012: The future of GLIBC Posted Apr 20, 2012 8:46 UTC (Fri) by jzbiciak (✭ supporter ✭, #5246) [Link]
Oops... I meant to post this upthread. Hit the wrong button while editing. *d'oh*
|
|||||||||||||