Why do you need to “tell” some “application”? Why do you need a “finder” if you know the absolute path already? Does this imply that “finder” always runs, ready to be told something?
Finder is macOS equivalent of Windows Explorer (maybe, it’s been a while). I assume Linux desktop suites have various similar processes. In other words, a second optional layer (with more features) to access runtime libc file manipulation api.
I usually write verbose code and use self-documenting function names, but to have such a limited set of verbs available can be frustrating. They could at least have used a proper dictionary and included all verbs. Then have a map of synonyms that are preferred, like instead of ‘create’ they prefer ‘new’ (which isn’t even a verb).
It’s one of those things wher eI’m sure it’s fine if you learn it. But it’s not DOS CMD, but also not bash.
So instead of improving CMD to have more features or just going all the way and offering an official bash implementation, they want me to learn a third thing. Just don’t have time for it.
Why u gotta hate on PowerShell like that? I like it. 😭
It might be nice and all that (I wouldn’t know), but it’s not a sub- nor superset of glorious POSIX
Probably because it’s the scripting language equivalent to Clippy. Ref.: Approved “verbs”
Boy oh boy would you hate AppleScript. This is what I have to type to throw files in the trash instead of deleting them.
tell application ”Finder” to delete POSIX file “/full/fucking/path/to/file”🤣
Why do you need to “tell” some “application”? Why do you need a “finder” if you know the absolute path already? Does this imply that “finder” always runs, ready to be told something?
Finder is macOS equivalent of Windows Explorer (maybe, it’s been a while). I assume Linux desktop suites have various similar processes. In other words, a second optional layer (with more features) to access runtime libc file manipulation api.
Explorers in Linux don’t work like this. They are just some app you can move your files with.
Yes. Finder is just some app you can move files with on macOS.
I really appreciate the consistency. People also dog it for being verbose to write but it makes it so much more legible.
/shrug
I usually write verbose code and use self-documenting function names, but to have such a limited set of verbs available can be frustrating. They could at least have used a proper dictionary and included all verbs. Then have a map of synonyms that are preferred, like instead of ‘create’ they prefer ‘new’ (which isn’t even a verb).
You don’t have to follow best practices though. You can name shit pretty much whatever you want.
No, but if you don’t the UI will nag at you just like Clippy did, which is my point.
Only if you haven’t disabled or dismissed the “problem”
Your opinion is wrong, Powershell must be banished
Bash already existed
I find objects much easier to work with rather than a bunch of string manipulation.
Just think of strings as the objects.
/waves magic wand
It’s one of those things wher eI’m sure it’s fine if you learn it. But it’s not DOS CMD, but also not bash.
So instead of improving CMD to have more features or just going all the way and offering an official bash implementation, they want me to learn a third thing. Just don’t have time for it.
It’s second to none if you have to get things done in a Windows environment, especially if dealing with Active Directory.
But if not, I don’t blame you for not picking it up. Right tool for the job and all that.
I do use it occasionally, but I gotta google for the command every time. So not exactly learning it.