Re:The truth about Goobuntu: Google's in-house desktop Ubunt...
by lucian1900 on Thursday August 30, 2012 @03:50AM
(#4453523)
It's a bit sad that many people attribute yum's slowness to Python. Most of that is because it builds an XML db every single time it runs.
[ Parent
| on HN ]
Re:The truth about Goobuntu: Google's in-house desktop Ubunt...
by ch0wn on Thursday August 30, 2012 @03:59AM
(#4453546)
Absolutely. Package managers are mostly IO-bound so there is no reason why a Python-based PM should be substantially slower than a C implementation.
Re:The truth about Goobuntu: Google's in-house desktop Ubunt...
by raverbashing on Thursday August 30, 2012 @04:24AM
(#4453605)
Except when they are calculating dependencies
But I agree with the yum sentiment, it really looks bad when compared to other solutions that existed: urpmi, apt-rpm, etc
Re:The truth about Goobuntu: Google's in-house desktop Ubunt...
by toyg on Thursday August 30, 2012 @11:39AM
(#4455136)
Yeah, i've always found that quite odd. Do you seriously need to refresh the package db every. single. time? I might agree that cron-based/user-initiated solutions are suboptimal (some users will just not bother, which is a security and support problem), but surely there is a compromise, like limiting the refresh to once a week.
(Cue some RedHat fanboi saying "but it's easy, you just do xyz" -- no, it's not easy unless it's default behaviour. Otherwise we might as well just run OpenBSD, because opening network ports every time you have to sneeze is "so easy".)