> What they don't do is let me build on things that already work in > arbitrary ways (especially in other languages and on other > machines...), and add to that when I have anything else that works. > Maybe they could, but then they would become a programming language > themselves.
Actually, they can Les and would not become a programming language themselves, that's what states and return codes are for. And you can call programs from other programs, but that's beyond the scope of the task. Actually you're blowing this all out of proportion. I'm talking about a simple wrapper to streamline actions normally required by issuing commands. You're thinking of my tool for your job, it won't work. It won't even work for my job, it will not write code. My tool will work for part of my job, just like the issued commands that it would replace. > That's fine if you want to buy a new vehicle for everything you > transport, Again, you miss the point. You don't but a new vehicle for everything you wish to transport. You buy 1 truck to do the transporting. It has noting to do with re-using. In fact, programming is all about reusing. I would be reusing lots of stuff. You can re-use everything either way. I can call grep or anything else, it is irrelevant. It is simply a different way to input something. That's it. Nothing more. Any extra stuff you pile on top will only confuse you. You don't have to like guis or programmers. But to say they are not useful or detrimental is a prejudice that can hurt you because it frankly is not a fact. -----Original Message----- From: Les Mikesell [mailto:lesmikes...@gmail.com] Sent: Tuesday, September 11, 2012 12:30 PM To: John Maher Cc: David Chapman; Mark Phippard; users@subversion.apache.org Subject: Re: general questions On Tue, Sep 11, 2012 at 11:02 AM, John Maher <jo...@rotair.com> wrote: > So there is NOTHING the gui can't do that the command > line can except take more time to do something. What they don't do is let me build on things that already work in arbitrary ways (especially in other languages and on other machines...), and add to that when I have anything else that works. Maybe they could, but then they would become a programming language themselves. > You're confusing the > steps to design an application with the steps to design a wrapper. Two > different animals and if you mix the two its like trying to pull a > trailer with a corvette. It may work, it may cause problems. It > definitely is not optimal. That's fine if you want to buy a new vehicle for everything you transport, never re-using anything you've done or being able to expand on it because you need a self-contained application for every operation. But, I like being able to do something once, then repeat it across a hundred machines with a simple script loop wrapping ssh. Or schedule it to run automatically. Or use some other remote tool to generate some of the options and/or inputs. Each tool does a step optimally and repeatably. Can you really beat what ssh does - or even grep? -- Les Mikesell lesmikes...@gmail.com