Re:Microsoft Replaces Command Prompt with PowerShell in Late...
by mhd on Friday November 18, 2016 @09:11AM
(#12986844)
By the way, where does the capitalized kebab case come from? Prior art or just Microsofts general hankering for capitalization (e.g. C#s Class.DoSomething() vs Java's Class.doSomething())?
[ Parent
| on HN ]
Re:Microsoft Replaces Command Prompt with PowerShell in Late...
by 794CD01 on Friday November 18, 2016 @02:10PM
(#12989254)
Wikipedia calls it Train-Case but doesn't provide a source. https://en.wikipedia.org/wiki/Letter_case#Special_case_style...
Re:Microsoft Replaces Command Prompt with PowerShell in Late...
by int_19h on Friday November 18, 2016 @04:32PM
(#12990252)
Note that it's not quite "kebab case". The dash only separates the initial verb from the object, but the rest of it is regular PascalCase. So Get-ChildItem, not Get-Child-Item.
PascalCase is well-established in the Microsoft developer ecosystem. It goes at least all the way back to Win16 and Windows 1.0 (it using the Pascal calling convention might have something to do with it, perhaps).
More importantly, it is used uniformly in .NET, and PowerShell builds on top of .NET, and deals with .NET objects directly, which have properties like e.g. `FullName`. So it makes sense for consistency.
Re:Microsoft Replaces Command Prompt with PowerShell in Late...
by Aaronepower on Friday November 18, 2016 @09:30AM
(#12986974)
What you're thinking of is PascalCase
Re:Microsoft Replaces Command Prompt with PowerShell in Late...
by pritambaral on Friday November 18, 2016 @09:39AM
(#12987018)
Your parent probably meant Kebab as in the dash (skewer-stick) between words.