8

Why the hell does windows not feature a generell purpose interpreted language? This is horrible! Seriously, out of the box this thing doesnt support anything!

Comments
  • 2
    It does - Batch. In newer versions there's Powershell.

    Oh and then there are the two evils JScript and VBScript you really don't want to touch. ^_^
  • 2
    @KeyWeeUsr Nope. Powershell is locked by default. Batch? Batch. Nothing more to say. And below... Holy, no.

    Edit: And regestry hacks, for heavens sake why the hell are you so uncoorperative, windows.
  • 0
    @vortexman100 locked? Anyway, Batch is quite nice if you get to know it better, but it's still a piece of shit, but still better than the two remaining ones :P
  • 0
    @KeyWeeUsr ExecutionPolicy, and this no doubleclick stuff.
  • 0
    @vortexman100 afaik you can work with Powershell even on an account without elevated permissions. What do you mean by that?
  • 1
    @KeyWeeUsr You have to allow unsigned ps scripts, which is a horror to do, because you eather have to enter stuff in the ps console, or hack the reg. Both is uncool. And, on top of that, you can not execute ps scripts via double click, because of "security reasons"...
  • 0
    @vortexman100 I see, now I tried to start a powershell script with doubleclick. I've never seen this thing before though (but I prefer Batch).
  • 1
    Probably because 98% of the people who use Windows couldn't give a rats ass about interpreted language support. Those who do... probably have the knowledge to set one up.
  • 1
    Yall seem to be to young to know about the interpreted scripting language by microsoft. It was VBScript. Yes it is bad. But daaamn was it mighty. Double clicking, integrated GUIs (in HTML), OS APIs, ...

    It IS bad, yes, but did you honestly expect something really good from Microsoft?
  • 0
    @darksideplease I've played with Batch and HTML when I was very young. Still I prefered Batch more than VBScript although I know what you can do with it.

    With that awesomely powerful(heh) VBScript came script kiddies. You can still experience them on SuperUser and sometimes even on StackOverflow(although they almost went to hell from that finally), so to VBScript for me it's just double amount of NOs in comparison of NOs a person would give to any of the remaining ones.
  • 2
    Batch is hardly programming.

    It's a series of console commands with some very basic flow control added in. But some of those flow controls (e.g. parenthesis defining if blocks) break other commands, and `call` doesn't always work as expected. The parenthesis also break variable expansion, since that happens only prior to beginning the interpretation of a line/"block". Later on, Microsoft added a "delayed variable expansion" extension, which requires a different variable syntax (!var! vs %var%), to enable vars being set and used within the same block.
    Vars also require a different number of prefixed %'s depending on their block nesting level, suggesting multiple parsing passes.

    The entire thing feels so *incredibly* hacky
  • 1
    PowerShell is your best bet. It's not really super hard to change the execution policy. If you're trying to send scripts to people that are not technically proficient, you could try something like this:

    https://gallery.technet.microsoft.com/...

    There's no equivalent to having Python or Ruby pre installed, but the ease of embedding on Windows sorta makes up for it.

    I don't know what else to say. I'm not a big fan of Windows but I've never seen this as an issue before.
  • 0
Add Comment