You are probably not alone in terms of your 'main vision' I have considered a lot of the same things. One problem is you never know the practicalities until you start writing code and evaluating for yourself according to your own preferences. (for example, can you tolerate having to use POD sections as part of your perl code, or is that an unacceptably inelegant kludge for you?; are you happy having to 'retrofit' your existing perl code in order to get it to run under dotNet?)
Another problem was eluded to by J ... specifically, the VB dotNet and the CSharp dotNet folks will bristle at the thought of having to look at "ACK!" Perl code. It shouldn't have to be that way, but there is a lot of language zealotry, and fear of "having to learn another language" ... even though the additional knowledge would probably make life easier for all involved. ...
That just seems to be the prevailing pattern.In reply to Re: Re: What are your experiences using PerlNET?
by dimar
in thread What are your experiences using PerlNET?
by jfroebe
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |