| |||||||||||||
|
| |||||||||||||
Go fish! (developerWorks)Go fish! (developerWorks)Posted Dec 3, 2008 22:24 UTC (Wed) by tyhik (subscriber, #14747)In reply to: Go fish! (developerWorks) by emk Parent article: Go fish! (developerWorks)
> Unix shells have stagnated in recent years.
Like much of that basic unix and internet stuff. The rfc793 dates back to almost thirty years
(Log in to post comments)
Go fish! (developerWorks) Posted Dec 3, 2008 23:16 UTC (Wed) by drag (subscriber, #31333) [Link]
I don't see mature and useful software as stagnating. Instead it just gets incorporated into larger and more complex hunks of software.
It's nice to see some change going on though.
Go fish! (developerWorks) Posted Dec 3, 2008 23:52 UTC (Wed) by JoeBuck (subscriber, #2330) [Link] "Stagnation" just means that 10-year-old code still runs. Better to write a new scripting language than to incompatibly change an old one.
Go fish! (developerWorks) Posted Dec 6, 2008 16:02 UTC (Sat) by dmag (subscriber, #17775) [Link]
That's exactly why fish is neat. The existing shells are ONLY used because they are ubiquitous. Nobody says "bash is an awesome programming language."
If you use Fish as your shell, then you can also use it to write Fish shell scripts. The "language" around the shell is a lot less arcane and has more conceptual integrity.
That said, I've tried to use fish as my main shell, and failed because it takes a while to learn. I couldn't figure out how to do "(sleep 1h; xmessage time to go) &".
|
|
||||||||||||