←back to thread

A Raycaster in Bash

(github.com)
235 points izabera | 1 comments | 20 Dec 24 22:25 UTC | HN request time: 1.118s | source
Show context
8n4vidtmkvmk ◴[21 Dec 24 07:31 UTC] No.42478062[source]▶
I never ceases to baffle me how we're still stuck with these mind bogglingly slow shells. Pure madness. I can maybe understand that some apps require all the vt100 weirdness or whatever, but probably 90% of apps just write to stdout and err. Surely we can blit some text to the screen a bit quicker and put the other 10% into some compat mode.
replies(1): >>42478262 #
1. PhilipRoman ◴[21 Dec 24 08:35 UTC] No.42478262[source]▶
Shells are slow (particularly bash), sure, but I'm not sure how the rest of your comment follows from that. The shell is not involved in interpreting terminal escape sequences in any way, and modern terminals are quite fast - I can render animations in a 350-column terminal and they are as smooth as can be, given the constraints. Besides, the whole premise of this post is that bash is the wrong language for raycasting, kind of like writing bubblesort in CSS.

>put the other 10% into some compat mode

There is nothing preventing that, just test if the string contains sane characters only and use a fast path for that. The problem is that there is no actual fast path for software text rendering, you still need to process ligatures, etc.