refterm VS PurefunctionPipelineDataflow

refterm, a terminal emulator proof of concept.

> licensing it so that they couldn’t even look at it

https://github.com/cmuratori/refterm/blob/main/LICENSE

It’s just GPL 2.0, what are you talking about!?

Are Microsoft employees vampires that will burn up instantly if they merely glance at GPL code or something?

This is sour grapes nonsense from Microsoft. “We don’t like your tone so we won’t even dignify your argument by considering it.”

At one point an MS employee said they would love to fix their code as suggested by Casey but he refused to even look at the YouTube video!

“I would love to hear your arguments but I refuse to listen to the sound of your voice.” is next-level dismissive.

You might also find https://github.com/cmuratori/refterm interesting.

Casey Muratori made a renderer/terminal a short while back. Might be a good reference of you intend to go that route. https://github.com/cmuratori/refterm

You keep complaining that it's not a fully working terminal. Casey, on the other hand, writes here: [1]

> These features are not designed to be comprehensive, since this is only meant to be a reference renderer, not a complete terminal.

[1] https://github.com/cmuratori/refterm#feature-support

After that post they did implement a full reference implementation:

https://github.com/cmuratori/refterm/commits/main

And there is movement in getting changes into the terminal itself:

https://github.com/microsoft/terminal/issues/10461

For a basic example of why you would want GPU acceleration, have a look at refterm: https://github.com/cmuratori/refterm

Even processes that you wouldn't think would be impacted by a terminal can be hurt relaly bad by your terminal's performance: your compiler's logs, etc. The GPU rendering part merely guarantees that your terminal sticks at 60FPS (or, whatever your refresh rate is) if the processing behind is efficient.

Implement relational data model and programming based on hash-map (NoSQL)

The Math-based Grand Unified Programming Theory: The Pure Function Pipeline Data Flow with Principle-based Warehouse/Workshop Model

I criticized "AMD Infinity Fabric Architecture" at the end of my article "Prediction: Intel will use "RISC-V plus x86 compatibility layer" or "RISC-V plus x86 heterogeneous computing architecture" to develop a new generation of "warehouse/workshop model" CPU".

What's more, you're being somewhat liberal with your "invention" dates here anyway. I'm sure you realize that anyone can review the commit history to see when content was added to the repo. As of Nov 2020, the day Apple announced a fully operational and tested, ready-to-ship silicon package the repo was a just series of bullet points listing out well-known concepts of functional programming sprinkled with some religious analogies and inspirational quotes. The farther you go back in the repo commit history, the less content is there.