3 ms·
I think it's flow order. But then you could say the same about forth. get_users filterActiveUsers sortByDateCreated getEmail Would be valid forth. But that d
by benj111 4y ago
I think it's flow order.
But then you could say the same about forth.
get_users filterActiveUsers sortByDateCreated getEmail
Would be valid forth. But that doesn't seem to match people's brain in the same way.
Maybe humans are weird and inconsistent?
Or maybe it's because it would end up as
& "file" -f 5 --bar get_users?
Although the shell doesn't really parse the options so you could cheat a bit and do
&Get_users -f "file" --bar 5
Which to me seems more readable than standard shell.
- xigoi 4y agoIn Forth, you have to reason about how many things each command takes off the stack and leaves on the stack, whereas with pipes, it's always exactly one thing.
- benj111 4y agoThat's true I suppose, but is the the only issue with forth? Or perhaps it's that a stack is good for certain things, but not for everything? If your language just consisted of map() you'd soon run into its limits.
- smcl 4y agoYeah I think it’s one of the less-hard things about Forth. For what it’s worth I quite enjoyed fiddling with Forth, and went through a bit of a “stack computing” phase. I never made the connection with the the pipe operator tho