You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ The doom-fire algo can push upwards of 180k a frame - results may vary! It is,
8
8
As a comparison, this is the younger sibling of a node variant ( https://github.com/const-void/DOOM-fire-node ).
9
9
10
10
# INSTALL
11
-
Tested on OX Sequia 15.2 / M1 w/zig 0.13...
11
+
Each MR tested on OX Sequia 15.2 / M1 w/zig 0.13 on OSX Kitty, VS Code, Alacritty, Terminal.
12
12
13
13
EDIT: Now tested on Artix Linux - links against libc to get the size of the TTY.
14
14
@@ -25,13 +25,15 @@ $ zig build run
25
25
26
26
# Results
27
27
* iTerm.app - ok
28
-
* kitty.app - great
29
-
* Terminal.app - poor -- seems to drop framerates
30
-
* VS Code - great
28
+
* kitty.app (OSX) - great
29
+
* Terminal.app (OSX) - poor -- seems to drop framerates
30
+
* VS Code (Linux, OSX) - great
31
31
* Warp - great
32
-
* Alacritty (artix linux) - great
32
+
* Alacritty (artix linux, OSX) - great
33
33
* Powershell/CMD
34
34
35
+
Note: Currently uses `u64` and thus is limited to x64 architecture, for now. In the future, will convert to a comptime approach for greater flexibility.
0 commit comments