On 18/12/2016 23:34, lee wrote: > Alan McKinnon <alan.mckin...@gmail.com> writes: > >> On 18/12/2016 18:47, lee wrote: >>> Rich Freeman <ri...@gentoo.org> writes: >>> >>>> The universe of Linux systems that are running Firefox but not >>>> Pulseaudio is fairly small at this point. >>> >>> Pulseaudio eats away about 10% CPU without any benefit whatsoever, not >>> to mention that it makes things more complex and less reliable. Why >>> would anyone use it? >>> >>> Developers might try to make their lifes easier by developing software >>> to the point where nobody wants to use it, except for the few developers >>> perhaps. With firefox, a policy like that contradicts their claims. >>> >>> >>> This is another issue which comes up quite often with FOSS. Developers >>> claim to be doing something in the interest of their users and are >>> asking for support. When you take a closer look, you find that they >>> don't, and when you offer support, they do not want it. >>> >>> Why can't they just say that they are making software for themselves the >>> way they want it and don't care about what anyone else says or wants? >>> It only gives reason to distrust someone when you find that they do not >>> do what they claim to be doing. >>> >> >> I think you are over-simplifying the situation here. Step back and look >> at the problem from the angle of "it's a bunch of people doing stuff" >> and not from a tech-centric angle. It's a people problem. >> >> You could make a valid case that the Mozilla devs are outright lying - >> they said they want xvy, and your offer to help provide xyz was >> rejected. But is it really that simple? I think it's more a case of the >> devs would like contributions for xyz and they don't mention the >> "everyone knows" "hidden assumption" of environment abc and general >> method def. Ahhhh, that's the usual tripping point. >> >> I don't know the specifics of your particular case, but my first >> approximation guess is that there's an abc and def in there which the >> devs didn't think to mention. Happens all the time, usually with >> stunningly obvious stuff that "everyone" thought "everyone else" knew >> about. Things like future roadmaps, planned features, and the individual >> personal preferences of each dev. >> >> I guess I'll saying don't be too quick to shoot from the hip - more >> looking less assuming is often the better path. > > It really is that simple because it is the way it turns out. It doesn't > matter /why/ it turns out that way. > > There is no assuming involved, and I have no reason to try to figure out > what hidden agenda a bunch of developers might have, or to make > assumptions about one. It won't change anything. > > That doesn't keep me from noticing that what is being said is very > different from what is being done. If the bunch of people wants to > change that, /they/ need to do so. >
I recommend you brush up on your social skills. Figuring out what people really mean as opposed to what they say (because those 2 never map exactly) is a very useful skill to cultivate, things are seldom as they appear to your eyes. -- Alan McKinnon alan.mckin...@gmail.com
