On Tue, 23 Jun 2009 10:39:53 +0800 明覺 <shi.min...@gmail.com> wrote:
> 2009/6/23 Hal Vaughan <h...@halblog.com>: > > > > On Jun 22, 2009, at 9:18 PM, 明覺 wrote: > > > >> On Mon, Jun 22, 2009 at 10:18 PM, John Hasler<jhas...@debian.org> wrote: > >>> > >>> 明覺 writes: > >>>> > >>>> yes, currently it's true, but I hope one day I will be able to take full > >>>> control of my system, and modify them as i like, if I have those other > >>>> language programmed softwares installed in my system, it will be hard to > >>>> maintain for me. > >>> > >>> If learning enough of another language to do maintainence is hard for you > >>> you aren't much of a programmer. Programming is not about knowing a > >>> language. > >> > >> Yes, language is just a tool, so I want to keep my tool simple and > >> powerful, I do not want so many similar tools with the same functions. > > > > Boy, I didn't realize that by "junior programmer" you meant you were that > > inexperienced in the field. I don't know if you realize that you've just > > basically said you are either unwilling or unable to understand the > > different reasons for different languages. > > > > EACH language is a tool, and each one is a DIFFERENT tool with a DIFFERENT > > purpose. > I will give an example to deny your opinion - "a DIFFERENT tool with a > DIFFERENT purpose" > Sql is a language for database operation, but what microsoft doing is > to use C# replacing sql, by linq. I don't like microsoft, but I like > the way they developing C#, the only one language for microsoft will > be C#, I guess. The only one language for microsoft is c#, oh wait, its visual basic, sorry wait a minute it's forms for the gui, assembly in the drivers in if you start digging you will find that half the system management is using scripts and batch scripts of one sort or another. > Then what's the only one language for linux? I think > it's C/C++. I'm afraid you are out of luck. All the init scripts are as the name sugests, scripts (you may get away without bash but you won't get away without sh which is basically simple bash). You probably should compile the kernel as compilation includes scripts (assuming you don't have problems with make files), emacs is out of the question as half of it is writen in elisp (variant of list). Vim may be ok, don't know. You can try dos, but the startup agian depends on batch scripts. OSx likes objectiveC more than c++, but there is also quite a bit of apple script and it's unix behind the scene which means perl, bash, python, etc. > > > > It is rarely a whim why a programmer picks one language over another. There I found that it's usually due to a whim and a bunch of buzz words. Usually it's the program you know, but quite often this is due to you picking your initial language to match the programming you like. I also do find that a lot of people, esspecially windows people BTW, tend to be narrow minded and lock into one programming language, usually it's c++ or c#. A lot of times its' the managers who don't know anything about programing that choose the language. > > are often several, if not many reasons why one language is more appropriate > > and better for a job than another is. > > > > But there's no point in continuing any discussion. You've made it quite > > clear you're too busy being right to care what anyone more experienced has > > to say -- unless it's what you want to hear. > > > > > > > > Hal > > > > -- > > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.orgwith a subject > > of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > > > > > > > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org