Pioneering with PowerShell

  • peter-757102 (6/26/2012)


    Not having worked with it, I did read some articles last year and was totally horrified by the language specifics and couldn't phantom somone getting language basics so wrong! A language needs to be precise and absolutely clear in its meaning, yes even scripting languages, but powershell code can be interpreted in many ways, most of them seem reasonable and useful in some situations, but only one is actually what it will do. That in itself constitutes a major fail I will argue here (I feel the same about perl for example)

    I would absolutely HATE to be forced to use such languages, but for some reason some people adore cryptic and mystic languages and confuse them for powerful. I always seen this as soem sort of cult factor!

    The mystic part will disapear if you know all the exact details and pay extreme attention to every letter, but at that point a scripting lanuage in my view already has failed!

    +1. I couldn't have said it better myself.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
    "Change is inevitable... change for the better is not".

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)
    Intro to Tally Tables and Functions

  • chrisn-585491 (6/26/2012)


    My main wish is that instead of creating YAPL (Yet Another Programming Language), Redmond could have leveraged a non-cryptic scripting language like Python. I enjoy learning, but the number of different language I need to accomplish my normal daily tasks is ridiculous!

    Redmond supports Python in Visual Studio 2012. It is up to developers whether it will get traction.

    Edit: spelling 'developers'.

  • I have already written some proof of concept application that can be extended using PowerShell scripting, and also using IronPython at the same time. Embedding PowerShell requires no more than dozen additional lines in your app, same for IronPython.

    Of course if you want to share some meaningful application state/features then you need to write proper classes and surrounding logic, but I found it to be very intuitive and easy (and I don't make living with everyday programming).

    Just remember that classes, properties and methods you want to be available in scripts must be public. I've lost couple of hours until I found this.

Viewing 3 posts - 16 through 17 (of 17 total)

You must be logged in to reply to this topic. Login to reply