###Batch questions should be allowed

I wouldn't want to see batch questions considered off topic. That would get silly pretty quick.

For example:

How about bash questions? You can write bash scripts as well. Maybe we should only allow bash questions if they're not scripting.

What's the definition of 'not scripting'? Three or so bash commands I suppose. Or maybe a lack of conditionals. Again, hard to draw the line.

Batch is pretty similar. They're really just commands at a Windows command prompt. Same thing with PowerShell. Where do you draw the line there? You can reference .NET in PowerShell pretty easily, but you also can (and probably should) perform many user-land tasks with PowerShell. Where do you draw the line here?

What about answers? What's the difference between "you can do this with a small batch script" and "write a program yourself"? Do we disallow PowerShell answers that are over 5 lines or reference .NET assemblies?

I think Jeff's answer is close, but rather than the person I would focus on the intent.

• Are you doing something in user-land? Ask on SU.
• Are you managing a rack of servers/login script/domain? Ask on SF.
• Are you in the weeds writing a tricky, complicated script? Ask on SO.

Batch questions should be allowed

I wouldn't want to see batch questions considered off topic. That would get silly pretty quick.

For example:

How about bash questions? You can write bash scripts as well. Maybe we should only allow bash questions if they're not scripting.

What's the definition of 'not scripting'? Three or so bash commands I suppose. Or maybe a lack of conditionals. Again, hard to draw the line.

Batch is pretty similar. They're really just commands at a Windows command prompt. Same thing with PowerShell. Where do you draw the line there? You can reference .NET in PowerShell pretty easily, but you also can (and probably should) perform many user-land tasks with PowerShell. Where do you draw the line here?

What about answers? What's the difference between "you can do this with a small batch script" and "write a program yourself"? Do we disallow PowerShell answers that are over 5 lines or reference .NET assemblies?

I think Jeff's answer is close, but rather than the person I would focus on the intent.

• Are you doing something in user-land? Ask on SU.
• Are you managing a rack of servers/login script/domain? Ask on SF.
• Are you in the weeds writing a tricky, complicated script? Ask on SO.

###Batch questions should be allowed

I wouldn't want to see batch questions considered topic. That would get silly pretty quick.

For example:

How about bash questions? You can write bash scripts as well. Maybe we should only allow bash questions if they're not scripting.

What's the definition of 'not scripting'? Three or so bash commands I suppose. Or maybe a lack of conditionals. Again, hard to draw the line.

Batch is pretty similar. They're really just commands at a Windows command prompt. Same thing with PowerShell. Where do you draw the line there? You can reference .NET in PowerShell pretty easily, but you also can (and probably should) perform many user-land tasks with PowerShell. Where do you draw the line here?

What about answers? What's the difference between "you can do this with a small batch script" and "write a program yourself"? Do we disallow PowerShell answers that are over 5 lines or reference .NET assemblies?

I think Jeff's answer is close, but rather than the person I would focus on the intent.

• Are you doing something in user-land? Ask on SU.
• Are you managing a rack of servers/login script/domain? Ask on SF.
• Are you in the weeds writing a tricky, complicated script? Ask on SO.

###Batch questions should be allowed

I wouldn't want to see batch questions considered off topic. That would get silly pretty quick.

For example:

How about bash questions? You can write bash scripts as well. Maybe we should only allow bash questions if they're not scripting.

What's the definition of 'not scripting'? Three or so bash commands I suppose. Or maybe a lack of conditionals. Again, hard to draw the line.

Batch is pretty similar. They're really just commands at a Windows command prompt. Same thing with PowerShell. Where do you draw the line there? You can reference .NET in PowerShell pretty easily, but you also can (and probably should) perform many user-land tasks with PowerShell. Where do you draw the line here?

What about answers? What's the difference between "you can do this with a small batch script" and "write a program yourself"? Do we disallow PowerShell answers that are over 5 lines or reference .NET assemblies?

I think Jeff's answer is close, but rather than the person I would focus on the intent.

• Are you doing something in user-land? Ask on SU.
• Are you managing a rack of servers/login script/domain? Ask on SF.
• Are you in the weeds writing a tricky, complicated script? Ask on SO.