4 ms·

Sure, which lends weight to the idea that the shell should be a more extensive programming language. Then you can pass an arbitrary Predicate<File> to the finde

Sure, which lends weight to the idea that the shell should be a more extensive programming language. Then you can pass an arbitrary Predicate<File> to the finder (which would likely just be a convenience function of about 5-20 lines), and receive a list of file objects for you to do what you want with That's the direction Powershell took, and to some extent was what other OSes were doing at the time of Unix. But Unix has become so ubiquitous and influential that we've forgotten that programs could pass more than ill-specified strings around, and that resources could implement richer interfaces rather than trying to force the file IO interface on every single one, regardless of how little sense that makes Worse is Better may have been a useful expedience in the 20th century, but we're long overdue repaying that technical dept, to get back some of the rich OS/environment features that other camps had got working almost half a century ago. The first step would be to stop putting "Unix philosophy" on a throne

hutzlibu 3y ago
"That's the direction Powershell took, and to some extent was what other OSes were doing at the time of Unix. But Unix has become so ubiquitous and influential that we've forgotten that programs could pass more than ill-specified strings around ... The first step would be to stop putting "Unix philosophy" on a throne " Well yes, but I think it will be hard or rather impossible to convince the unix crowd of anything good coming from windows.
- c00lio 3y ago
  There are still tons of stringly-typed interfaces in powershell.
  - hutzlibu 3y ago
    I did not say I am a big fan of the powershell or windows in general. But I would still like the few good ideas integrated into linux ..
iopq 3y ago
Unix being stringly-typed is a huge problem. For example, I found a flatpak of a system monitor and thought it was portable. Turns out, it parses `ps` output directly, but it's not compatible with BusyBox `ps` output https://github.com/hakandundar34coding/system-monitoring-center/issues/168# https://github.com/hakandundar34coding/system-monitoring-cen... the author literally doesn't care since it works with coreutils `ps` it's a culture problem
- riddley 3y ago
  Doesn't ps just parse /proc entries these days? Seems like an odd hill for that dev to die on.
  - iopq 3y ago
    I suggested for him to parse /proc in that issue tracker, but he kind of stopped reading my suggestions

hutzlibu 3y ago

"That's the direction Powershell took, and to some extent was what other OSes were doing at the time of Unix. But Unix has become so ubiquitous and influential that we've forgotten that programs could pass more than ill-specified strings around ... The first step would be to stop putting "Unix philosophy" on a throne " Well yes, but I think it will be hard or rather impossible to convince the unix crowd of anything good coming from windows.

c00lio 3y ago
There are still tons of stringly-typed interfaces in powershell.
- hutzlibu 3y ago
  I did not say I am a big fan of the powershell or windows in general. But I would still like the few good ideas integrated into linux ..

iopq 3y ago

Unix being stringly-typed is a huge problem. For example, I found a flatpak of a system monitor and thought it was portable. Turns out, it parses `ps` output directly, but it's not compatible with BusyBox `ps` output https://github.com/hakandundar34coding/system-monitoring-center/issues/168# https://github.com/hakandundar34coding/system-monitoring-cen... the author literally doesn't care since it works with coreutils `ps` it's a culture problem

riddley 3y ago
Doesn't ps just parse /proc entries these days? Seems like an odd hill for that dev to die on.
- iopq 3y ago
  I suggested for him to parse /proc in that issue tracker, but he kind of stopped reading my suggestions