Linked by brynet on Thu 15th Jul 2010 16:55 UTC
QNX As of April 2010, a silent change was made on Foundry27, users with a myQNX account could no longer checkout/update their copies of the QNX SVN repositories and a vague Wiki page was created "detailing" some licencing clarifications.
Thread beginning with comment 434085
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: The Obvious:
by hussam on Tue 20th Jul 2010 15:14 UTC in reply to "RE[5]: The Obvious:"
Member since:

ArchLinux sucked balls the only time I tried it. Waay overhyped POS. Atleast at that date.

Archlinux is nice. But it lost the KISS distribution personality when it got infested by users who want less package dependencies at the expense of broken dependencies for example when the 'optdependency' thing was introduced.
run ldd on your /usr/bin and /usr/lib/ and you'll find broken binary dependencies which can be fixed by installed 'optdependencies'. This breaks KISS philosophy because it doesn't confirm with how upstream designs applications.

Reply Parent Score: 2

RE[7]: The Obvious:
by aliquis on Tue 20th Jul 2010 15:44 in reply to "RE[6]: The Obvious:"
aliquis Member since:

When I tried it (To its defence it may have been pre-1.0 (0.7? 1.4? Don't remember.)) it managed to break USB devices (switch of /DEV-system) and ALSA (probably just an upgrade / linked to old libs / whatever, the mixer stopped working) between updates.

When things break I prefer to be the one who's f--ked up. The days then I accepted and sorta saw the fun in things breaking and "being hard to manage" has long passed by. And if it would happen I would have had enough of dealing with my own shit instead of the maintainers.

Back in those days I used to use FreeBSD but just wanted to see where Gentoo and the other "omg it's soo good I can't believe it's Linux(!? ;) )"-distributions where at for the time being.

Things can break in the BSDs to, but when it happen in the OS it's most likely due to an upgrade and documented with a solution in the upgrade documentation. And if it happens with ports/pkgsrc you're most likely responsible for it yourself.

With things like Solaris it's not like Sun would have said "oh well f--k this way of doing things, we throw it out and replace it with something else for now and let things break until we've fixed it all!"

And well, I think I prefer that approach. But Linux development in general seem to always has preferred new ideas, fast implementations and testing/fine tuning over time until you get the desired result over making something which work as it should at the cost of having to wait until it's ready / a more slow and steady approach to adding new functionality.

And as far as total development tempo goes the Linux method seem to be the better one.

Edited 2010-07-20 15:46 UTC

Reply Parent Score: 2