Singularity is a kernel written in C#, not a shell. Although I can't see why they couldn't use the code from powershell once they have the code in the kernel nailed down and complete.
I'd prefer that they don't; PowerShell's design philosophies go in direct opposition against
Singularity's (and against .NET/Microsoft's in fact), namely in the fact that the PowerShell team carelessly encourages code to break down at runtime, and they don't honor very basic .NET
such as Unicode for strings.
PowerShell Scripts continue to use ".PS1". ... You might write a .PS1 script which takes advantage of a cmdlet/feature that is only available in V2. If you send this to someone that has PS V1, it will fail "in some way and at some time".
"Now if you think it's hard doing a lowercase 'm' at 9pt or 10pt, try doing utsu (鬱), which has 8 horizontal strokes. If you have 8 horizontal strokes, you need 15 pixels to show them all, right?
8 black and 7 whites between 'em. But at 10pt, you only have 9... or 14, or whatever. So what do you do there? Well the solution in the past was they embedded bitmaps. They had to do stroke reduction. Can't show all the strokes.
The Japanese are just going to go ape. We've had incredible feedback from the Japanese government people looking at this."
My dad's a designer; he did some typography stuff back when we were in Japan. He does publishing and printing now. Sure enough, he went ape when he saw Meiryo.