Microsoft insults dev then takes credit for their idea

1. Windows Terminal

   1 516 97,702 9.5 C++

   The new Windows Terminal and the original Windows console host, all in the same place!

   

   > Please take into consideration that Casey's definition of the solution as "simple" can sound quite insulting as well.

   It can sound insulting only to people who originally claimed that what Casey suggested requires "doctoral level research into performance". Only to then implement exactly what he suggested.

   > If someone stated that something is "simple" with an overtone of "are you blind", instead of showing more humility

   Please re-read the original GitHub issue from the start: https://github.com/microsoft/terminal/issues/10362

   He is there trying to understand an issue, providing suggestions etc. And generally being baffled how a modern terminal on a modern machine can output text at something like 5 frames per second.

   After that Windows Terminal team barges in with "what you’re doing is describing something that might be considered an entire doctoral research project in performant terminal emulation" to... only do exactly that later.

   And what Casey said was going to be simple is this: https://github.com/microsoft/terminal/issues/10362#issuecomm...

   Tell me how this is insulting to anyone except the people who now claim that "oh we'd been aware about this approach before Casey opened the issue"?

2. CodeRabbit

   coderabbit.ai featured

   CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

   

3. refterm

   2 38 1,649 2.0 C

   Reference monospace terminal renderer

   

   >most of the code in the parser/renderer part of the terminal is unnecessary and just slows things down. What this code needs to do is extremely simple and it seems like it has been massively overcomplicated

   He means exactly what he says. Notably, refterm had almost no optimization applied to it.[0] The massive performance increase was entirely due to non-pessimization.[1]

   >refterm actually isn't very fast. Despite being several orders of magnitude faster than Windows Terminal, refterm is largely unoptimized and is much slower than it could be. It is nothing more than a straightforward implementation of a tile renderer, with a very simple cache to ensure that glyph generation only gets called when new glyphs are seen. It is all very, very simple. A more complex codebase that parsed Unicode and rendered glyphs itself would likely be much faster than refterm for many important metrics.[0]

   [0] - https://github.com/cmuratori/refterm

   [1] - Refterm Lecture Part 1 - Philosophies of Optimization - https://www.youtube.com/watch?v=pgoetgxecw8

4. cpp-docs

   3 12 1,511 9.9 PowerShell

   C++ Documentation

   

   Now can you get Microsoft to fix their broken implementation of FMA? (see https://github.com/MicrosoftDocs/cpp-docs/pull/3526 for details)

Suggest a related project