OSNews

I mean the "feel of the system", there are some tools that are trying to be more user friendly than efficient.
A lot of userland tools are abandoning Unix principles, especially the Linux ones. For example: "no output on succesful operation", do you know any pkg install tool which remains silent if you install something?
another example: "one task one tool" Why would you need fetures inplemented into a command line tool, if you can use |grep or |sort for those tasks?
I`m just conservative when it comes to Unix.

I mean the "feel of the system", there are some tools that are trying to be more user friendly than efficient.

For me, an inefficient program is not friendly, especially not to me, the user... :-)

"A lot of userland tools are abandoning Unix principles, especially the Linux ones."

I always thought the Linux style utilities were suffering from the GNU long options (where BSD's tools usually use the simple options), such as "tar xjf /dev/fd0" or "usbdevs -dov", in opposite to "gphoto2 --get-all-raw-data --and-some-more-options=here").

"For example: "no output on succesful operation", do you know any pkg install tool which remains silent if you install something?"

Ah, I see now. The same goes for editors like vi: it does what you tell it to do and only speaks to you if something went wrong. No answer == success. One advantage: You can automate things using shell scripts and don't need any redirection > /dev/null 2>&1 in order to keep the output silent if there is no problem, or just to keep your startup log free of blahblah.

Another idea comes to my mind thinking about your argument: While Linux is more like WYSIWYG (what you see is what you get), BSD (and other UNIXes too) are more like YAFIYGI (you asked for it, you got it). No clue where I read this. Okay, that's very general, don't mind...

"another example: "one task one tool" Why would you need fetures inplemented into a command line tool, if you can use |grep or |sort for those tasks?"

That's an experience I'm very comfortable with. Each tool solves a specific range of tasks what it is intended for. Nothing more. There are wrappers that utilize other tools or mechanisms (such as gmencoder to mencoder, transcode etc. or portinstall / portupgrade to the ports and packages subsystem), this is a valid option.

"I`m just conservative when it comes to Unix. "

Be sure, I do understand this. Because english is not my native language, I first had not an idea what you were talking about. Now, after the examples given, I do understand.

If you're using many different UNIX systems (SGI IRIX, HP-UX, Solaris, FreeBSD, OpenBSD, NetBSD etc.) and you need to get along with them, you're happy to have the usual commands working the same way - and having them available everywhere, be it grep, sort, uniq, sed or just sh. Of course, they're different, but I'm right when I say the many Linusi have differences, too, allthough they are all called "Linux". But this has been mentioned before.