251–259 of 259 posts
Earlier quoted context omitted.
Funny guy, everyone understood that I meant The X Window System™ .
Well, it goes to demonstrating expertise, doesn't it? Hard to know something if you don't know what it's called, innit?
I love Cmder, it's superior to cmd.exe in all possible ways, but from time to time it just stops working. Now I understand better why.
G'ah - PLEASE read the posts about which you're commenting - Cmder is a terminal/Console, not a shell. Cmd.exe is a (headless) command-line shell. A shell accepts input from a terminal/Console and emits text to its connected terminal/Console to be displayed back to the user. All this is covered in some detail in the posts thus far.
Earlier quoted context omitted.
Well, re: >1. Does your machine use a spinning disk for its system drive, or SSD? This really shouldn't be a question regarding the performance of a terminal window . If cmd.exe starts fast regardless, then so should Powershell if it is going to replace it. And on that note, on a new laptop with an SSD I can see a difference between Powershell and cmd.exe execution-to-prompt-ready time (however small that latency is)…
I am not comparing performance of a terminal window - Cmd and PowerShell both run connected to the same terminal app - Windows Console (conhost.exe) as discussed ad nauseum in the posts that are the subject of this thread. But you're comparing a 30+ year old command-line shell that was built in 1989 to primarily provide compatibility with MS-DOS, with a modern object-based shell that runs atop the .NET CLR and provid…
That's not an excuse for the startup time of a shell not being instantaneous on a modern system.
To harness the power, I write Powershell scripts (yay no more batch files), but it's just too annoying to experience the startup lag to use the shell for the simplest tasks (e.g. simply running a console application).
That shouldn't be the case.
PS: "modern object-oriented" was all the hype in the 80-s. It's not an excuse for a performance hit today :)
Earlier quoted context omitted.
All I know is that the last time I installed Windows 10, I still had to edit the registry for it to find DejaVu Sans Mono. If that has changed recently, that's fantastic!
Console now enumerates and allows selection of monospace TTF fonts. Alas, as one of our dev's says often "Fonts are just files containing collections of lies"! Some fonts claim to only contain monospace, glyphs, but don't and include non-monospace or irregularly sized chars. Others just lie completely. But if you have well-formed TTF fonts, that express correct metdata, and ARE monospace, then they should be selectab…
Earlier quoted context omitted.
Well, it goes to demonstrating expertise, doesn't it? Hard to know something if you don't know what it's called, innit?
That’s ridiculous. The full name is super cumbersome and not really intuitive. Most people just call it X...
... how is X more cumbersome than "X Windows"?
> Most people just call it X
Right. Because that's its name.
Earlier quoted context omitted.
I am not comparing performance of a terminal window - Cmd and PowerShell both run connected to the same terminal app - Windows Console (conhost.exe) as discussed ad nauseum in the posts that are the subject of this thread. But you're comparing a 30+ year old command-line shell that was built in 1989 to primarily provide compatibility with MS-DOS, with a modern object-based shell that runs atop the .NET CLR and provid…
Sure, sure, more functionality. That's not an excuse for the startup time of a shell not being instantaneous on a modern system. To harness the power, I write Powershell scripts (yay no more batch files), but it's just too annoying to experience the startup lag to use the shell for the simplest tasks (e.g. simply running a console application). That shouldn't be the case. PS: "modern object-oriented" was all the hype…
If you're running Hyper, note that this alone takes 6s to (warm) start Cmd on my 16GB RAM Core-i7 Surface Pro 4.
PowerShell takes ~1.2s to (warm) start connected to Console, while also starting a half dozen modules and scripts in my PowerShell user profile.
PowerShell takes < .7s to start when run with `-NoProfile`
I like the post, it seems like they are good guys doing a good work on an unrewarding application. It is interesting the insight thet are giving with this article: - MS is improving on Windows Console only because of WSL - the design of the Windows Console was flawed since the beginning and remained unchanged to something like 30 years. Flaws includes: - using Console API instead of sending characters / cannot work r…
X Window has a good design? Only because it allowed competing tool kits on top of it ("Provide mechanism rather than policy. In particular, place user interface policy in the clients' hands.") Besides the fact that the X libs are almost universally reviled and nobody used them as soon as they could (Motif, Qt, Gtk, etc.). The core concept, that of network part is actively being abandoned right now, see the Wayland ef…
X does. "X Window" might not, but it probably isn't in widespread use.
I like the post, it seems like they are good guys doing a good work on an unrewarding application. It is interesting the insight thet are giving with this article: - MS is improving on Windows Console only because of WSL - the design of the Windows Console was flawed since the beginning and remained unchanged to something like 30 years. Flaws includes: - using Console API instead of sending characters / cannot work r…
X.