[mythtv] #10305 heads up, mysql.txt removal + config.xml changes + UPnP fixes

[Raymond Wagner]

On 5/4/2012 02:16, Tim Phipps wrote:
> Quoting Raymond Wagner <raymond at wagnerrp.com>:
>>  The only value it has for use in bash is when trying to access the 
>> database directly, and if you need to access the database directly, 
>> you can spend the effort writing whatever you're doing in a "proper" 
>> programming language with native MySQL bindings and proper type 
>> handling, rather than something that is just going to clumsily wrap 
>> the `mysql` shell client.  Any such language is going to have some 
>> form of XML parser available, and not have any problem dealing with 
>> the config.xml.
>
> Please don't take offence but the above comes across as snobbish. 
> "Proper" programming languages come and go, sh is a Posix standard and 
> is here to stay.

I don't mean to imply that Bourne (Again) is bad, or that it shouldn't 
be used, but rather that it should be used for its intended purpose.  It 
is a shell script, and as such, its intended purpose is to manage 
external applications.  It has relatively little built in functionality, 
as most of is functionality is intended to be provided by calling 
external applications.  The language is of course Turing complete, 
meaning with sufficient effort, you can program it to do anything any 
other language could do, but that doesn't mean it will be easier than 
doing it in some other language.  When you start doing things like 
accessing databases, you have long since exceeded the point at which you 
should switch to a language with a more expansive tool set.