3 ms·

Just to clarify, I do not hate MSFT. I just don't have the ability to implement such things and just curious whether it is feasible (in reasonable time) or not.

Just to clarify, I do not hate MSFT. I just don't have the ability to implement such things and just curious whether it is feasible (in reasonable time) or not. If the actual code is not available maybe someone can fork the Terminal code? Or if that does not get around the legal stuffs, maybe take the idea and go from there?

forgotpwd16 5y ago
You cannot use Casey's code (GPL) in Terminal (MIT). But he has explained his model. Issue is iirc what he proposed and how Terminal works significantly differ.
- dundarious 5y ago
  Yes, I’m skeptical that WT will incorporate his design, as it is a big design change. There’s no way to just “plug it in” somewhere, without replacing the beating heart of WT. It would be great if they did that though, and I’d applaud them for it.
  - forgotpwd16 5y ago
    Apparently they did and in retro-perspective it was indeed that simple. (Simple as in they made their own custom renderer afterall.) https://devblogs.microsoft.com/commandline/case-study-how-many-colors-are-too-many-colors-for-windows-terminal/ https://devblogs.microsoft.com/commandline/case-study-how-ma...
    - dundarious 5y ago
      Brilliant! Haven't had time to read it yet, but that's great to hear.
      - dundarious 5y ago
        I think Casey did a lot of other great work on more correct and speedy non-ASCII support, and very efficient scrollback (in both memory and time cost), etc. It's been a while, but I think the atlas approach is also different. But kudos for what seems to be a good step. I'm curious to see some data on the resulting performance and memory usage (presuming the latter is mostly unchanged).