Here's from the FreeBSD Journal magazine (Sep/Oct 2014) about UFS, how it's good for science related data storage on FreeBSD:
issue.freebsdfoundation.org
This makes it sound very good. I'm happy with it. The only issue is when my harddrive fails, though that's about the harddrive, and I have important data backed up. I use TMPFS for compiling and such.
I'd like to see a
NeXtaw implementation (Xaw toolkit) that's ported to XCB.
or even halfway to XCL. Then this be its own ecosystem that remains simple. A few BSD-like window managers ported to XCB
or halfway to XCL. Edit - NeXtaw's last update is 20 years old. libXaw3dxft is the only modern Athena Widget toolkit that has Unicode and Freetype, thus internationalization support. This is a better target to port to XCB.
LibCanberra being forked or replaced for basic sounds. If forked, simply remove ALL graphical dependencies from it. Make dbus optional on it. Make it separate from Pango, which that can have graphical dependencies. Pango can be indicated by message from a LibCanberra install, or made optional, but not used as the default install. Pango would be the only exception for libCanberra options related to graphical dependencies.
Making Bonjour (
net/mDNSResponder) or
net/openmdns the default Zeroconf implementations. Allow Avahi as an option, but not be the default.
Improve the dependencies structure, where some options or versions aren't hardset. This is a little difficult to explain. Let's say, a port asks for a specific version of ImageMagick and many versions conflict with each other. Installing a port, makes an existing version of ImageMagick be removed, and replaced with another version or x11 variant.
Make this improved either through port messages, or have it so dependency requirements are met by a class that for example is of ImageMagick port. Back to a previously made point, let "Zeroconf" be the dependency, and this will be as a class. Allow it so the user can select whether they want Bonjour, openmdns or Avahi from
make.conf. Also, make CUPS not be a hardwired dependency, let it be installed and queried for to the user by pkg install message. "Print" can also be a dependency class which includes CUPS as a choice.
Another example is how window managers and Xorg are kept separate, because of this, upgrading a window manager doesn't require all of Xorg to be reinstalled. There's often a chain reaction of dependency requirements that requires much to be rebuilt, including from the toolchains and other dependencies. In some case, use messages to tell that more dependencies are needed for a certain functionalities.
In short, dependency classes, where a dependency can be satisfied by a few varying specific options, along with package messages for dependency features.
Edit - package messages was referring to
pkg-message that exists under many individual ports in the
/usr/ports/ tree. This message shows when those ports are finished compiling, and can be shown using
pkg info -D
.