←back to thread

Show HN: Term.everything – Run any GUI app in the terminal

(github.com)
1080 points mmulet | 2 comments | 09 Sep 25 13:16 UTC | HN request time: 0.001s | source

I made a built-from scratch Wayland Compositor to display any GUI app* in the terminal! I think there is a lot of unexplored potential in custom Wayland compositors, a lot of really cool things you can embed existing applications into! So, I started with embedding apps into the terminal because that is the easiest input/output (output is just utf-8 and I use the great `chafa` library for that, and I just read from stdin for the input).

If you have any other ideas for cool Wayland compositors, let me know. I purposedly wrote 80% the app in Typescript to appeal to the most developers and attract cool contributions (I do all drawing with the familiar Canvas2D api, so if there is interest, I can also fork this out into a cool Terminal canvas, let me know!)

I have a blog post here about how I did it, but it’s pretty high level and non technical, so please ask if you have any questions.

[How I Did It](<https://github.com/mmulet/term.everything/blob/main/resource...>)

*technically only Wayland apps and x11 apps with Xwayland. But on Linux that’s mostly everything.

1. tclover ◴[11 Sep 25 07:20 UTC] No.45208769[source]▶
I tried recently once again to ditch Windows for Linux. Everything kinda worked, but the MediaTek Wi-Fi drivers were janky and my speed was like 10x slower than it should’ve been. After spending about 10 hours messing around with configs, I realized I was doing literally everything except what I actually wanted to do when I turned on the PC… so I just went back and installed LTSC Windows again.
replies(1): >>45209782 #
2. saghm ◴[11 Sep 25 10:07 UTC] No.45209782[source]▶
I don't really understand the relevance of this comment to this thread, but since it's here...I remember running into something somewhat similar when trying to dual-boot Windows for something on a machine I already had Linux installed on, and while I can't remember whether it was actually MediaTek or not, I think it might have been. If my recollection is correct, I ended up figuring out that having the wifi configured to 1 Gbps in Windows somehow reverted the wifi to only 100 Mbps in Linux, and the only way for me to fix it was to boot back into Windows and switch it to whatever it had been by default (I think 100 Mbps?). Not sure if this is something you care enough to actually try out or not, but I figured it couldn't hurt to mention!