Comment by thriftwy

4 years ago

Nope!

It's just that in corporate world, developers rarely do what they think is relevant for them.

The people who did Windows terminal probably cared a lot about COM or WinAPI or maybe CS, but I think it's fair to imagine how they were not fans of text-oriented interfaces. It just did not occur that they should be extracting last bit of performance here. People can type just that fast, after all.

11 comments

thriftwy

Reply
zadjii  4 years ago

TBF we've actually maintained the Windows Console for the better part of 5 years and we're incredibly passionate about performance. We live and breath in the commandline. Performance has always been one of our P1 priorities, because improvements to the console have second-order impacts on the entire commandline ecosystem.

There is an engineering tradeoff though - we've only got so many devs and at a certain point you have to say "good enough for now, we'll come back to this, let's go do this other thing for now". The Terminal is faster than conhost was, and that's a good place to start, but I don't think anyone things we're done working on the Terminal, and we're certainly not done working on its perf ;)

Tabular-Iceberg  4 years ago

Yeah, that’s another problem, the software industry as a whole is horrendously bad at getting requirements right.

tasogare  4 years ago

Windows terminal is a shit show. The dev blogs posts are all about useless features such as image background while fundamentals like unicode input are still broken.