On Sat, Mar 7, 2015 at 6:11 PM, T.J. Duchene <t.j.duchene@???> wrote:
>
>> "Go look at the code, it's open" is a common "argument" i hear from pro-systemd advocates. Curious. About looking at the code: have you personally audited chrome's code, top to bottom, OpenBSD-style? 'Cos if you haven't - it is a big piece of software -, well your argument is moot
>

>  Nuno, when I say this, I'm not trying to be rude, or nasty or mean.    The fact that you don't like Google is noted, and accepted.

>
> If you aren't going to make the effort to look at the code, please do not pass judgment on the authors or their efforts. Otherwise, you are offering only second hand knowledge: hearsay and not fact. That's not an argument associated with systemd, that is the whole point of open source. It is actually about the level of trust. No one can possibly argue that the code is tainted or not when they have not reviewed the code. Nor has anyone on this list likely to have reviewed the vast majority of the code for all of a Linux distribution. Either Devuan trusts the community to police the code or it doesn't.

Unfortunately i don't have time to look at every bit of code of the
software i use. I do trust the majority of open-source software out
there, without looking at its code. I don't think i need to look at
the code for that.

> Just to be clear, I did not advocate "Chrome" at any point. Chromium is not Chrome. A derived software is not the same as the original. Chrome is made from Chromium, not the other way around. Much the same way, LibreOffice is NOT the original OpenOffice, nor is Lotus Symphony.

Me neither and i wrote "chromium" when i actually meant "chrome", my
bad. Since you didn't answer the original question i'm going to assume
you did look at chromium's code. Please share your insights. While i
inderstand the stability of forking a process for every tab i don't
see the benefit of the performance penalty. Maybe i'm wrong.

I - personally - use chromium sometimes as i, as you've noticed,
dislike Google yet some IE-ish sites work better on chromium than they
do on firefox. Chromium seems fast but lacks a few plugins i use in
Firefox. Unfortunately, they're both memory hogs (as far as my
experience with them goes). Hence my original suggestion: for a distro
that's still trying to get on its feet, a lightweight browser would
probably be best, like midori, dillo or something else. I don't think
the effort of eventually tweaking firefox or chrome (i said
eventually) is worth it at this moment.

Still, that's the beauty of open-source: even if one of these two
browsers gets chosen, i can, if i want, use something else. As can
you.

> I think after this, I'm going to lessen responding to the general list. I'm *not* pointing fingers at you, Nuno or anyone's behavior. I am just as guilty of the same, but any time I decide to spend on Devuan could be more productive: better spent packaging or coding. I "totally get" the need to vent, or just rant sometimes - but the constant antagonism toward certain software, their authors, and the paranoia is starting to get to me. Some of the discussions have been great! I especially liked the one on languages. However, most seem to go nowhere.

Indeed any time spent on packaging or coding is time well-spent, thank
you. I do try to vent as little as possible and try doing so in a
rational and civilized manner. However, as has recently happened here
on the list, maybe some cultural nuances flew by me (english is not my
native language) and i may've offended you somehow. If so, my
apologies.

> Is there a dev list available where I can track the progress of Devuan toward Alpha?

This discussion has been brought up before and the general consensus
was not to split this list into dev- and user-. My take on that at the
time was that not splitting makes sure both sides (if you see sides; i
don't -- and didn't say you do) stay in touch and blurr the lines a
bit -- it's sane for both to "keep each other in check" and to know
what the other is doing. Obviously this is only my opinion.

Cheers,
Nuno