News for hackers. Stuff that matters.

A comment on Making Debian Responsible For Its Actions. Parent comment

Re:Making Debian Responsible For Its Actions by davidw on Tuesday September 28, 2010 @04:23AM (#1734974)
> Of course Zed's hyperbole is rampant but that's what makes him fun to read.

Does he want to be 'fun to read' or fix a problem? Because pissing all over other people's hard work and attributing nefarious motives to them to boot is not a good way of fixing the problem.

> The way Debian attempts to micromanage rubygems is insane and ends up breaking under real world environments. Why do they persist?

Good question - why not do some research and find out?

(BTW, I'll add that there are good reasons not to use Debian's gem packages, and that I disagree with the 'pile-on' downvoting of the parent post, even if I disagree with what he said)

[ Parent | on HN ]
Re:Making Debian Responsible For Its Actions by regularfry on Tuesday September 28, 2010 @06:41AM (#1735221)
Being fun to read gives him a disproportionately large audience, which increases the chances of things getting fixed.
[ Parent | on HN ]
Re:Making Debian Responsible For Its Actions by gloob on Tuesday September 28, 2010 @09:00AM (#1735522)
So would filing a bug report.
[ Parent | on HN ]
Re:Making Debian Responsible For Its Actions by FooBarWidget on Tuesday September 28, 2010 @03:12PM (#1736860)
It would not. The Debian maintainers created the status quo deliberately. Causing a stir would be far more effective than another bug report.
[ Parent | on HN ]