5 ms·

Windows Terminal Preview 1.11 Release

23 points by zadjii 5y ago

travisporter 5y ago
Does anyone else notice a lag in opening windows terminal compared to powershell? I see it in this demo as well.
- zadjii 5y ago
  Yea, there's always been a little bit more delay. The problem with comparing the Terminal to conhost (the vintage console) is that conhost was _nothing_. It was a dead simple window that drew to a GDI surface. There was basically no other UI to initialize. With the Terminal, we've got to instantiate a XAML Island to host the WinUI content. That's unfortunately not as lightweight as _instantiating absolutely nothing_. It's something we're working with the WinUI team with pretty aggressively, because it impacts everyone who wants to use WinUI.
  - siproprio 5y ago
    It's been slow like this (and with lots of user complaints!) since always! Perhaps you guys should borrow some of those Microsoft research phd folks to improve terminal performance[1]. [1]: https://www.youtube.com/watch?v=99dKzubvpKE https://www.youtube.com/watch?v=99dKzubvpKE
markus_zhang 5y ago
I wonder whether they would consider the Casey Muratori improvement in future releases.
- zadjii 5y ago
  We're actually tracking a bunch of follow ups from that whole discussion. The big ol' list is under https://github.com/microsoft/terminal/issues?q=is%3Aopen+is%3Aissue+label%3AArea-Performance https://github.com/microsoft/terminal/issues?q=is%3Aopen+is%..., though the most specific thread is https://github.com/microsoft/terminal/issues/10461 https://github.com/microsoft/terminal/issues/10461. The prototype was fairly promising!
  - AnIdiotOnTheNet 5y ago
    I find the discussion around the licensing hilarious after what Casey had to put up with in the initial issue. https://github.com/cmuratori/refterm/issues/17 https://github.com/cmuratori/refterm/issues/17
  - markus_zhang 5y ago
    Wow good work friends!
Datsundere 5y ago
Even the demo video was so slow
- zadjii 5y ago
  It's possible the demo-er was intentionally leaving pauses for the viewer to parse what was taking place. It's also possible that PowerShell just takes a little while to load up the profile. That's why I stick with cmd.exe (within the Terminal of course, I'm not a barbarian) :P
  - moogly 5y ago
    PowerShell Core, especially, is an absolute dog to start up.
  - watersb 5y ago
    PowerShell can take thousands of milliseconds to start up on my shiny new computer. Hold your breath for five seconds as it looks around for stuff.
- siproprio 5y ago
  Notice the lag when dragging the tooltip! It takes seconds for the tooltip to appear! Being microsoft, wouldn't be surprised if they started deleting negative feedback.
  - AnIdiotOnTheNet 5y ago
    Reading through Microsoft's responses to feedback about the slowness is depressing: "XAML is just like that". Between that and Casey's interaction over WT's performance, is it any wonder software keeps getting slower and fatter? The developers a big important IT company like Microsoft is hiring don't really have any knowledge, experience, or give-a-damn in the realm of making things not suck.
  - zadjii 5y ago
    You know, that's just gotta be a recording artifact. I'm playing with the tooltip drag/drop right now and it's instantaneous. > Being microsoft, wouldn't be surprised if they started deleting negative feedback. You know, you're entitled to your opinion. But negative feedback is just as important as positive feedback. Hell, there's probably no team in Windows that's as salty at the rest of the company as the Terminal team :P But I resent the opinion that we'd go out of our way to delete negative feedback. Constructive negative feedback is a real strong indicator that there's more work to be done. And trust me, there's lots of work to still be done.

23 points by zadjii 5y ago

travisporter 5y ago

Does anyone else notice a lag in opening windows terminal compared to powershell? I see it in this demo as well.

zadjii 5y ago
Yea, there's always been a little bit more delay. The problem with comparing the Terminal to conhost (the vintage console) is that conhost was _nothing_. It was a dead simple window that drew to a GDI surface. There was basically no other UI to initialize. With the Terminal, we've got to instantiate a XAML Island to host the WinUI content. That's unfortunately not as lightweight as _instantiating absolutely nothing_. It's something we're working with the WinUI team with pretty aggressively, because it impacts everyone who wants to use WinUI.
- siproprio 5y ago
  It's been slow like this (and with lots of user complaints!) since always! Perhaps you guys should borrow some of those Microsoft research phd folks to improve terminal performance[1]. [1]: https://www.youtube.com/watch?v=99dKzubvpKE https://www.youtube.com/watch?v=99dKzubvpKE

markus_zhang 5y ago

I wonder whether they would consider the Casey Muratori improvement in future releases.

zadjii 5y ago
We're actually tracking a bunch of follow ups from that whole discussion. The big ol' list is under https://github.com/microsoft/terminal/issues?q=is%3Aopen+is%3Aissue+label%3AArea-Performance https://github.com/microsoft/terminal/issues?q=is%3Aopen+is%..., though the most specific thread is https://github.com/microsoft/terminal/issues/10461 https://github.com/microsoft/terminal/issues/10461. The prototype was fairly promising!
- AnIdiotOnTheNet 5y ago
  I find the discussion around the licensing hilarious after what Casey had to put up with in the initial issue. https://github.com/cmuratori/refterm/issues/17 https://github.com/cmuratori/refterm/issues/17
- markus_zhang 5y ago
  Wow good work friends!

Datsundere 5y ago

Even the demo video was so slow

zadjii 5y ago
It's possible the demo-er was intentionally leaving pauses for the viewer to parse what was taking place. It's also possible that PowerShell just takes a little while to load up the profile. That's why I stick with cmd.exe (within the Terminal of course, I'm not a barbarian) :P
- moogly 5y ago
  PowerShell Core, especially, is an absolute dog to start up.
- watersb 5y ago
  PowerShell can take thousands of milliseconds to start up on my shiny new computer. Hold your breath for five seconds as it looks around for stuff.
siproprio 5y ago
Notice the lag when dragging the tooltip! It takes seconds for the tooltip to appear! Being microsoft, wouldn't be surprised if they started deleting negative feedback.
- AnIdiotOnTheNet 5y ago
  Reading through Microsoft's responses to feedback about the slowness is depressing: "XAML is just like that". Between that and Casey's interaction over WT's performance, is it any wonder software keeps getting slower and fatter? The developers a big important IT company like Microsoft is hiring don't really have any knowledge, experience, or give-a-damn in the realm of making things not suck.
- zadjii 5y ago
  You know, that's just gotta be a recording artifact. I'm playing with the tooltip drag/drop right now and it's instantaneous. > Being microsoft, wouldn't be surprised if they started deleting negative feedback. You know, you're entitled to your opinion. But negative feedback is just as important as positive feedback. Hell, there's probably no team in Windows that's as salty at the rest of the company as the Terminal team :P But I resent the opinion that we'd go out of our way to delete negative feedback. Constructive negative feedback is a real strong indicator that there's more work to be done. And trust me, there's lots of work to still be done.