10 ms·
I looked at the repository, and quake mode is priority 3, and the settings UI is priority 0. Quake mode is more upvoted than settings UI. And don't get me sta
by siproprio 6y ago
I looked at the repository, and quake mode is priority 3, and the settings UI is priority 0.
Quake mode is more upvoted than settings UI.
And don't get me started on WinUI 3. Everytime I look at the WinUI roadmap, it gets pushed further, with the wanted features removed, and irrelevant things prioritized.
And that's by the same team that shipped UWP 1.0
- zadjii 6y agoUpvotes are not the only way of measuring the popularity of an issue, though they certainly are the easiest. The settings UI has had a _ridiculous_ number of issues filed asking for the same thing, while quake mode had much fewer. For whatever reason, people are more willing to upvote the existing quake mode issue, rather than file a new issue, compared to users asking for the settings UI. Perhaps there's some commentary on the type of users asking for those features that could be made based on their behavior. Plus, I'm literally working on a [quake mode spec](https://github.com/microsoft/terminal/pull/9274 https://github.com/microsoft/terminal/pull/9274). We're reviewing that next week. I've got a prototype.Quake mode required a lot more infrastructural work than the SUI, so it was my opinion that we might not be able to get to it this release cycle (i.e. 2.0). As it turns out, we're closer than I thought we would be. We can make progress on lots of different things all at once - there is surprisingly, more than one dev on the team. The roadmap doc is not something that we update all that frequently. We've got better things to do - like work on features :)