4 ms·

The big lesson Plan 9 seemed to have learned is that maintenance is a drag and a hinderance. find may be objectively better than du | grep for the user, but onc

The big lesson Plan 9 seemed to have learned is that maintenance is a drag and a hinderance. find may be objectively better than du | grep for the user, but once introduced then the developers have to essentially maintain the same thing twice and carry that baggage forever into the future. In a parallel universe where Unix did not take on so much baggage, perhaps it could have even naturally evolved towards Plan 9 and Plan 9 would have not been a necessary break. But then, like Plan 9, maybe Unix would have never rose up to see any widespread use to make that evolution significant. Tradeoffs, as always.

mikepurvis 3y ago
I always feel guilty that find . | grep <pattern> is easier for me than remembering how find's flags work. But I think it's really a case of my brain rejecting exactly the redundant baggage you're speaking of here.
- salawat 3y ago
  What's hard about "find . -regex <regex> -exec <stuff> /;" Hardest thing that comes to mind is there's some slight portability differences to look out for between GNU find and BSD find that may require a quick man dive with relation to the max depth handling, but that's about it.
  - eschneider 3y ago
    Ah...find's "swiss army chainsaw" mode. So, so useful. :)
  - herewulf 3y ago
    You just answered your own question because it's "\;" not "/;". And the "{}" placeholder syntax isn't exactly intuitive either (maybe there is some connection to awk or sed? I only know enough of those to be dangerous). I've used find extensively in the past two decades and even read the man page (gasp) on occasion, but it's one coreutils command that I have always found cumbersome. I recently discovered fd and I have a feeling that I will be switching to that where I can, muscle memory be damned.
Hendrikto 3y ago
> The big lesson Plan 9 seemed to have learned is that maintenance is a drag and a hinderance. So they chose to just never finish the OS instead.
- randomdata 3y ago
  No, they did choose to finish the OS. The final release came quite a number of years ago.

mikepurvis 3y ago

I always feel guilty that find . | grep <pattern> is easier for me than remembering how find's flags work. But I think it's really a case of my brain rejecting exactly the redundant baggage you're speaking of here.

salawat 3y ago
What's hard about "find . -regex <regex> -exec <stuff> /;" Hardest thing that comes to mind is there's some slight portability differences to look out for between GNU find and BSD find that may require a quick man dive with relation to the max depth handling, but that's about it.
- eschneider 3y ago
  Ah...find's "swiss army chainsaw" mode. So, so useful. :)
- herewulf 3y ago
  You just answered your own question because it's "\;" not "/;". And the "{}" placeholder syntax isn't exactly intuitive either (maybe there is some connection to awk or sed? I only know enough of those to be dangerous). I've used find extensively in the past two decades and even read the man page (gasp) on occasion, but it's one coreutils command that I have always found cumbersome. I recently discovered fd and I have a feeling that I will be switching to that where I can, muscle memory be damned.

Hendrikto 3y ago

> The big lesson Plan 9 seemed to have learned is that maintenance is a drag and a hinderance. So they chose to just never finish the OS instead.

randomdata 3y ago
No, they did choose to finish the OS. The final release came quite a number of years ago.