Date: Fri, 28 Apr 2006 02:14:41 +0200 From: Danny Pansters <danny@ricin.com> To: freebsd-questions@freebsd.org Cc: Gary Kline <kline@tao.thought.org> Subject: Re: scripting languages... Message-ID: <200604280214.41292.danny@ricin.com> In-Reply-To: <20060427235828.GD2601@thought.org> References: <20060427024158.GA71123@thought.org> <1146188104.7085.8.camel@bursar> <20060427235828.GD2601@thought.org>
next in thread | previous in thread | raw e-mail | index | archive | help
To get back to the original question, I think there's one crucial part: libraries. Or modules, or function sets or whatever they're called in [ pick language ] sphere. It's the extra stuff that you can easily add or import which makes a language worth while, whether it's interpreted or not. That's whjat defines how much functionality it has for you. Now for scripting languages I'd say perl (if you like) or python (if you like, I do) or perhaps ruby (if you like), as all have a lot of libraries/modules you can easily incorporate and build upon. If all you're going to do is shell stuff, then I'd say you should use portable sh scripting and nothing else. Or one higher level scripting language (by preference), but not a "shell-plus". Like bash... Or if you really want C syntax , use C ;-) IMHO, Dan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200604280214.41292.danny>