nicholasrq

6 ms·

1.
by nicholasrq 7mo ago
on that one i'm guilty, not gonna lie
2.
by nicholasrq 7mo ago
every terminal emulator uses PTY internally no matter if it's GPU accelerated or not
3.
by nicholasrq 7mo ago
nope, fully from scratch
4.
by nicholasrq 7mo ago
it does have framebuffer of course because you need to store actual text somewhere. in this case framebuffer stores structs that contain text (char), its styles and dirtiness all chars are rasterized into atlas (sprite, if you want) contain
5.
by nicholasrq 7mo ago
well, for most of the applications you probably don't need it. it's like a nice to have thing. it really kicks in is when you have a highly dynamic interface (mostly TUI do this). something like btop or similar. in this case rende
6.
by nicholasrq 7mo ago
i intentionally avoided windows because it's conceptually different from UNIX(-like) systems. for an early prototype like this it's just easier to manage because i share 90% of the codebase. real fork is just in the way i render t
7.
by nicholasrq 7mo ago
well, if it works, it works, right? sure requires some cleanup but i'm not saying it's super stable and all. my intention here is to bring some attention and maybe gain some feedback on what i'm building
8.
Attyx – tiny and fast GPU-accelerated terminal emulator written in Zig(github.com)
19 points by nicholasrq 7mo ago|16 comments
9.
Epist – a terminal email client built on a custom TypeScript TUI engine(github.com)
1 points by nicholasrq 7mo ago|0 comments
10.
Semos – family of terminal apps and tools for building TUI apps(semos.sh)
2 points by nicholasrq 7mo ago|0 comments
11.
React-based TUI framework based on Yoga and react-reconciler. Full Flexbox(github.com)
1 points by nicholasrq 7mo ago|0 comments
12.
Relic – a missing secrets artifact for Node and Edge(npmjs.com)
1 points by nicholasrq 7mo ago|0 comments