-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> It would require people to not only do it for the sake of their
> projects,
> but for the whole BSD people. Even those who really piss you off in
> other projects.
>
> Because someday, those projects will live on without us. We'll pass on
> like everyone.
>
> Am I alone thinking this ?
You're completely right, diversity always hurts an ecosystem *rolls
eyes*
Let's be serious here, each of the mainstream BSDs have their places,
and I'm glad they're separate. I'd run OpenBSD on a soekris box on
the fringe of my network, FreeBSD on my 4-way Opteron interactive
server, and NetBSD on my Tamagotchi (http://en.wikipedia.org/wiki/
Tamagotchi).
They all have their places, by merging them you lose a lot of the
focus of keeping them separate. Besides some largely impractical
"good feeling" that we'd derive from unifying the projects, there's
absolutely no reason to unify them. And to be frank, some people you
don't want to work together, there's a reason DragonFlyBSD forked
from FreeBSD, and there's a reason OpenBSD forked from NetBSD; not to
say this is a bad thing at all, but trying to make people get along
to volunteer their time on a project is outright retarded. Developers
who like the goals and team of the FreeBSD project will gravitate
that way, same with OpenBSD, NetBSD and DragonFlyBSD.
NetBSD isn't having trouble because of OpenBSD forking from it, or
from FreeBSD's recent innovations, NetBSD is having trouble because
of actions taken by those within the project, unification
accomplishes nothing in the realm of practicality.
Cheers,
- -R. Tyler Ballance
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
iD4DBQFE+A6PqO6nEJfroRsRArKFAJjgWGbVS3w1BmmYPThRTRoTWxLvAJsEpzpK
4ZUDjBGTprGcNsOgYYrszw==
=SMpu
-----END PGP SIGNATURE-----