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.
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.
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.
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
