| Follow @MaximBurgerhout
near Leiden, between The Hague and Amsterdam, The Netherlands
Hi! I'm Maxim, a solution architect and evangelist in Red Hat's Benelux team.
Red Hat radiates open source in every possible way, which makes it the perfect company to work for, for an open source enthusiast like me.
As part of my job, I spend a lot of time talking to customers and presenting at conferences about Red Hat's portfolio. Key element is how our solutions can help organizations solve actual business problems.
I also maintain a blog and YouTube channel about the systems and cloud management products in our portfolio. It's fairly technical, but please take a look at the videos by clicking the YouTube icon below, and check out my blog at 100things.wzzrd.com.
Authored Comments
I wouldn't know about them being deprecated, but the fact that you cannot nest them is reason enough for me not to use them. I also prefer the syntax of $(foo) over `foo`: it's quite clear where a $(foo) statement starts and ends, even if you do $(foo $(bar)). That's much harder with `foo `bar``.
Hi Mossaab,
thanks for your remarks! (And sorry for my own late reply... Vacation happened :))
I'm not a huge fan of the env statement myself, partially because my scripts are all aimed at Linux, so Bash in /usr/local/bin/bash, like on BSD, is not a big risk. The second, more prominent reason, is that an env statement potentially uses a different bash than the system one, with potentially unexpected results. (Granted, this is less of a problem with bash than with, say, Python.)
The double brackers is a fair point, and something I'll take into account for future versions of this - or other - articles.
The usage() function is a nice one as well, thanks!