I assume you mean “why use these instead of file-manipulation commands in bash?”
I use both.
There are a handful of tasks that are easier in dired than bash.
Making small modifications to filenames that aren’t amenable to programmatic changes. You can just toggle the read-only flag on a dired buffer, edit the filenames, and then hit C-c C-c when done.
Marking a set of files to perform an operation on where that set cannot trivially be expressed using tools in bash. Think, oh, “which movies do I like enough to want to keep around”. This is especially handy when moving a number of files to another directory, which I think is why people often like the two-pane approach of orthodox file managers. Dired is not an OFM, but it can act like that if you have two dired windows open, using the other as the default target for the operation.
Dealing with filenames containing obnoxious-to-type characters like weird Unicode stuff. If I want to delete the one file in a directory whose name consists of a bunch of kanji, it’s easier to just manually select it in a list.
Navigating where I usually want to see the contents of each directory. I’ll often navigate around in dired while building up up an emms playlist. Browsing a list of movies to play.
EDIT: It’s also not really a file manager, but I do use ncdu to see what’s taking up space on a disk. I’ll also use du -h|sort -h|less, but ncdu is, like file managers, more convenient when just browsing around the tree and looking at each as one does so, while manually selecting a few items to operate on (deleting).
EDIT2: I’ll also add that virtually all of the people I know in person who love OFMs – I’m in the US – are from Eastern Europe, moved to the US from Russia, Ukraine, Romania, etc. I dunno why that is. Maybe just spreading along language lines. Maybe there are or were issues with switching between Cyrillic and Latin character stuff akin to my above irritation with kanji. But someone from Eastern Europe might have more input to answer your question.
EDIT3: The link I provided above for OFMs has a very long discussion from the author on why he likes OFMs (though not all terminal file managers are OFMs, many, like Midnight Commander, are). Reading it, I’d say that there’s a lot of overlap with how Emacs works with dired+TRAMP+eshell and some other Emacs packages, though they accomplish similar goals in a different way – sort of making integrated functionality that spans network file transfer, file management, text editing, file archive access, console commands, with a common toolset available for all. Would be quicker to learn an OFM than Emacs, though Emacs is gonna provide a considerably-larger set of functionality if you’re willing to spend the time on it.
EDIT4: There are also a number of OFMs in Emacs, like Sunrise Commander, so I guess I shouldn’t really treat it as an either-or matter.
It was probably /usr/sbin you’re thinking of rather than /usr/bin. IIRC – don’t quote me on this – Red Hat puts it in non-root user paths by default, and Debian doesn’t.
Yeah, the reason for this is that sometimes Debian doesn’t enable Plymouth splash screens by default, so you just see the text stuff. It actually annoys me a bit.
I always go through and turn off all the stuff that’s covering up the diagnostic information that I want to see, myself.
Mmmm…okay, but the parent comment I was responding to does have a point in that there are some benefits to blocking Javascript above and beyond just trying to deal with tracking. Like, if you’re on a laptop, there are sites that will burn a lot of CPU time – and hence battery life – doing nothing useful. Or, on an older machine, it can speed up page loading.
My issue is just that unless you’re going to turn it on yourself on a site-by-site basis, killing off Javascript breaks too much of the Web today. It was a viable option to just have on back when there was a meaningful portion of the world that didn’t have Javascript available and web developers designed pages to deal reasonably with its absence and you were willing to deal with flipping it off on specific sites to deal with the occasional breakage…but today, it’s a huge portion of the Web that doesn’t work without Javascript.
My understanding – and I’m not a New Yorker – was that he has been often credited with reducing crime in NYC. Part of that was, as I recall, by cracking down on minor crimes, things like aggressive panhandling, with the idea that that was kind of a gateway drug to more-severe crime.
I don’t know whether that approach or him in particular was responsible for it, or whether it was other phenomena at the time – my gut is that changes like that usually aren’t just driven by one person – but my understanding was that crime did considerably fall off around the time, and crime was something that a lot of New Yorkers had been really upset about.