On Fri, Jan 2, 2015 at 6:51 PM, Les Howell <hlhow...@pacbell.net> wrote:
My question, then would be what about applications that require input
at
startup? How does this fit with the practice of chainables such as
grep
-n temp *| tail -f | tee > foo.txt
The original premise of *nix systems was to have tools that did one
thing and did it well, that could be piped to create complex
operations
without writing new code. Is that to be considered archaic? You
cannot
create windowed applications that can even approach that capability,
so
from that view point the system is somewhat crippled. And as a
developer, I have several utilities that take advantage of the
pipeliining capability to do things that make my life easier. Windows
makes the programmers job easier, provides a crutch to get people
going
on computers, but misses the point of having a tool to create new
things
for single uses or very limited uses.
How about one of the most basic developer toolsets, that of diff and
patch? If you have never used that, you should learn.
There are others, but I generally have them built into scripts and
speaking of scripts, where do they fit in your applications
definition?
It's all kind of a moot point. The terminal is here to stay. Upgrading
Software to display command line programs will help people find gcc,
but isn't going to help anyone discover patch or diff, and it won't
help anyone install the development libraries she needs to get work
done.
In the other thread, we seem to have found some amount of consensus
that there should be a graphical way to install development tools. A
discussion that could actually result in some change to Fedora is more
interesting to me than philosophical points on the nature of *nix.
Happy Friday,
Michael
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
