Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

What can TCC v36 do that PowerShell 5.1 cannot do?

Aug
2,799
144
I asked Microsoft CoPilot;

What can TCC v36 do that PowerShell 5.1 cannot do?

I asked Microsoft CoPilot to format the response for posting to the JPSoft Forums.

This is the output that I received.

---

1. Native command-line features PowerShell cannot replicate

Instant directory navigation enhancements:
  • Directory history stack (PUSHDIR, POPDIR, DIRS)
  • Directory aliases (ALIAS /D)
  • Extended CD syntax (partial matches, fuzzy matches)

PowerShell has Push-Location/Pop-Location, but no:
  • persistent directory history
  • directory aliasing
  • fuzzy directory matching

---

2. Wildcards and file matching far beyond PowerShell's capabilities

TCC supports:
  • Regular expressions in filenames
  • Advanced wildcards ([!abc], ranges, character classes)
  • Conditional wildcards
  • Date/size/attribute filters directly in the filename expression

PowerShell can filter after enumeration, but cannot:
  • use regex in the path
  • embed attribute/date filters in the path
  • use TCC's extended wildcard engine

---

3. Built-in variable functions (hundreds)

TCC has hundreds of built-in variable functions for:
  • string manipulation
  • date/time math
  • hashing
  • encoding/decoding
  • file metadata extraction
  • INI parsing
  • numeric formatting
  • environment manipulation

PowerShell can do these things, but:
  • requires .NET calls
  • requires custom functions
  • requires modules
  • is slower for many micro-operations

---

4. Internal commands that PowerShell simply does not have

Examples:

File operations:
  • COPY /S /A:... with attribute-based selection
  • MOVE /H /S /A:...
  • DEL /S /A:...
  • FFIND (fast text search)
  • LIST (paged viewer)
  • VIEW (file viewer with hex mode)

PowerShell can approximate these, but:
  • not with the same speed
  • not with the same switches
  • not with attribute-based path filters
  • not with built-in viewers

---

5. Interactive shell features PowerShell lacks entirely

TCC includes:

Command dialogs:
  • file selection
  • directory selection
  • input boxes
  • message boxes

PowerShell has no built-in GUI dialogs (requires WinForms/WPF code).

Command line editing:
  • filename completion with wildcards
  • directory completion with fuzzy matching
  • history search with regex
  • programmable tab completion

---

6. Built-in search, scanning, and text processing tools

TCC includes:
  • FFIND (fast grep-like search)
  • FINDSTR enhancements
  • LIST (interactive viewer)
  • TPIPE (pipeline text processor with dozens of filters)

PowerShell can do text processing, but:
  • not with TCC's speed
  • not with TCC's pipeline filters
  • not with interactive viewers

---

7. Batch-file compatibility and enhancements

TCC supports:
  • full CMD.EXE batch syntax
  • plus hundreds of extensions
  • structured exception handling in batch files
  • DO loops with ranges, lists, files, arrays
  • IFF/THEN/ELSE syntax

PowerShell cannot:
  • run enhanced CMD batch logic
  • use TCC's structured batch control flow

---

8. Shell-level performance advantages

TCC is optimized for:
  • extremely fast directory scanning
  • extremely fast wildcard expansion
  • extremely fast environment variable operations

PowerShell 5.1 is slower due to .NET object overhead.

---

9. Features that PowerShell can do, but only with heavy code

TCC does them natively:
  • INI file read/write
  • JSON parsing (via TPIPE)
  • Hashing (MD5, SHA1, etc.)
  • Base64 encode/decode
  • FTP/HTTP operations
  • ZIP/UNZIP
  • File attribute filtering in path expressions
  • Timers and profiling

PowerShell requires:
  • .NET classes
  • modules
  • custom scripts
  • external utilities

---

10. Features PowerShell simply cannot do at all

Unique to TCC:
  • On-the-fly alias expansion with parameters
  • Command plugins loaded at runtime
  • Internal command dialogs
  • Extended wildcard engine
  • Directory navigation with fuzzy matching
  • Interactive file viewers
  • Batch exception handling
  • Built-in pipeline text processor (TPIPE)

---

Summary

TCC is a supercharged command shell.
PowerShell is an automation language.

They are complementary, not competitors.

---
 
Back
Top