SCIENTIFIC-LINUX-USERS Archives

January 2017

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Mon, 2 Jan 2017 10:47:21 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
I'll just continue with bash before I start with anything else since I 
just recently started playing around with bash. Thanks for all the 
responses about my question.

Also Happy New year to everyone on the list and best wishes for 2017 :)



On 2016-12-31 07:38, Steven Haigh wrote:
> On 31/12/16 17:12, Nico Kadel-Garcia wrote:
>> I'd suggest learning bash first. Many complex perl, python, php, etc.
>> tools are actually wrappers for a few lines of shell.
> 
> Yeah, I was going to suggest this too..... Your biggest thing will be
> shell scripts - they hold everything together.
> 
> There's not much that you can't do in bash - but there are a lot more
> things that are much more complex / dedicated that you'd be better off
> in a language like perl.
> 
> The big thing is learning how to think in logical steps. When to use 
> if,
> for, while etc etc. Once you've got a grip on the basics, the only real
> difference between languages is what specific formatting you give to 
> the
> options to keep its compiler happy.
> 
> bash is something you'll use every day - so its probably easy to deal
> with from the start.

ATOM RSS1 RSS2