I really want to support open source efforts. But I really can&#x27;t if there&#x27;s a project developed without any googling before the first line of code. We have terminal multiplexers. I don&#x27;t know but I wouldn&#x27;t be surprised if he had one when computer still meant big tubes and real typewriters being connected to screens. This project doesn&#x27;t offer anything that screen or tmux can&#x27;t do, as far as I understand the README. And it also doesn&#x27;t mention its biggest two competitors.<p>Please, to save your own time and energy (if not the time and energy of other people) search for a solution before you build one. Only if you have found the two or three solutions that the community likes most and you are still unsatisfied, only then start coding. And set yourself a real goal about what your tool should be doing that the others don&#x27;t.<p>In this example tmux is quite interesting. Screen was around for ages. But a few things were not possible with the screen code base, like splitting your screen in whatever way you want. And some things simply were not really user friendly, like the config. With this in mind a guy named Nicholas Marriott sat down and started coding his alternative.<p>That&#x27;s how you do it. Stick his picture on your wall. Follow his path. Start with googling for your problem, not with coding.<p>PS: I think the idea of having different desktops in graphical shells in fact came from people wanting to have the terminal multiplexing feature in their graphical environment as well. So Desk is like taking your calculator apart to develop a method to calculate with pen and paper.