starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Feature Request: Its 2020, new scripting language #5904

New Issue
Closed
opened 2026-01-31 00:24:56 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 00:24:56 +00:00
Owner
Copy Link

Originally created by @komawoyo on GitHub (Jan 14, 2020).

Description of the new feature/enhancement

Its 2020 and while we are at it with a new Windows Terminal, we should also design a new robust and strongly typed data oriented (?) shell scripting language. Maybe members can voice their opinions (ie rather use python instead of bash/batch because...). Also the following may be useful.

https://bit.ly/30cIddA
https://mywiki.wooledge.org/BashPitfalls
https://www.experts-exchange.com/articles/673/Advanced-DOS-batch-pitfalls.html

.... I mean this would be an addition to what we have already to remain backwards compatible similar to what is happening with ConPTY/ConHost.

Originally created by @komawoyo on GitHub (Jan 14, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement Its 2020 and while we are at it with a new Windows Terminal, we should also design a new robust and strongly typed data oriented (?) shell scripting language. Maybe members can voice their opinions (ie rather use python instead of bash/batch because...). Also the following may be useful. https://bit.ly/30cIddA https://mywiki.wooledge.org/BashPitfalls https://www.experts-exchange.com/articles/673/Advanced-DOS-batch-pitfalls.html .... I mean this would be an addition to what we have already to remain backwards compatible similar to what is happening with ConPTY/ConHost. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). -->
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 00:24:56 +00:00
claunia commented 2026-01-31 00:24:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 14, 2020):

Maybe something like Powershell?

@zadjii-msft commented on GitHub (Jan 14, 2020): Maybe something like [Powershell](https://github.com/PowerShell/PowerShell)?
claunia commented 2026-01-31 00:24:58 +00:00
Author
Owner
Copy Link

@komawoyo commented on GitHub (Jan 14, 2020):

Possibly but

https://www.red-gate.com/simple-talk/sysadmin/powershell/a-plethora-of-powershell-pitfalls/
https://www.red-gate.com/simple-talk/sysadmin/powershell/a-plethora-of-powershell-pitfalls-part-2/

@komawoyo commented on GitHub (Jan 14, 2020): Possibly but https://www.red-gate.com/simple-talk/sysadmin/powershell/a-plethora-of-powershell-pitfalls/ https://www.red-gate.com/simple-talk/sysadmin/powershell/a-plethora-of-powershell-pitfalls-part-2/
claunia commented 2026-01-31 00:24:58 +00:00
Author
Owner
Copy Link

@PaulBags commented on GitHub (Jan 14, 2020):

Not python, mandatory indentation in a terminal would be a nightmare.

@PaulBags commented on GitHub (Jan 14, 2020): Not python, mandatory indentation in a terminal would be a nightmare.
claunia commented 2026-01-31 00:24:58 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 14, 2020):

Hey all,
Thanks for jumping in and suggesting this.

Scripting languages, especially those with interactive components, are a rasonably contentious matter. There are articles extolling the virtues and pointing out the pitfalls that you can probably find for any language ever invented. Nonetheless, we need to choose one that makes the most palatable tradeoffs for everyone (users, developers, system administrators, those with interactive and automated scripts, etc.) and move on.

The choice Microsoft has made is Powershell. It fits a lot of the categories you originally enumerated: it's robust, it's data-oriented, and it's at least somewhat-typed.

Powershell is finally reaching a point where people reach for it instead of batch, and people want to use it on Linux and macOS. It would set us back ten or fifteen years and incinerate an immense amount of community goodwill if we were to stop it, abandon it (or leave it in maintenance mode) and move on to "greener pastures." We're just not going to do that, and this issue isn't really the best place to have the hypothetical discussion about what-if-we-would.

There isn't anything actionable for my team or my project here, and I have a feeling that this thread could easily get out of hand, so I'm going to get out ahead and close + lock it.

Thanks for your understanding!

@DHowett-MSFT commented on GitHub (Jan 14, 2020): Hey all, Thanks for jumping in and suggesting this. Scripting languages, especially those with interactive components, are a rasonably contentious matter. There are articles extolling the virtues _and_ pointing out the pitfalls that you can probably find for any language ever invented. Nonetheless, we need to choose one that makes the most palatable tradeoffs for everyone (users, developers, system administrators, those with interactive and automated scripts, etc.) and move on. The choice Microsoft has made is Powershell. It fits a lot of the categories you originally enumerated: it's robust, it's data-oriented, and it's at least somewhat-typed. Powershell is finally reaching a point where people reach for it instead of batch, and people want to use it on Linux and macOS. It would set us back ten or fifteen years and incinerate an immense amount of community goodwill if we were to stop it, abandon it (or leave it in maintenance mode) and move on to "greener pastures." We're just not going to do that, and this issue isn't really the best place to have the hypothetical discussion about what-if-we-would. There isn't anything actionable for my team or my project here, and I have a feeling that this thread could easily get out of hand, so I'm going to get out ahead and close + lock it. Thanks for your understanding!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Feature Needs-Tag-Fix Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#5904
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?