source is a beautiful viewer for me, right?

nice viewer I have, right?         
                                        
it is based on the so-called "transfusion" method
by stack". Of course.                  
images of texts represent
command sequences:              
                                        
 LD HL,XX                        
        PUSH HL                         
                                        
Everything is clear here.                           
Why am I writing this text? - you ask
you.                                     
                                        
and here's why:                            
It seems to me that this very method of "overflow-
"stack" is completely unfair
considered inappropriate, cumbersome and
etc.                                    
however, such an opinion is nothing more than
than a stereotype.                        
daemon.)                               
closed by a self-sufficient chain of thoughts
lei in your mind.                     
which needs to be OPEN.          
                                        
STACK OVERFLOW IS NOT AT ALL
BY AN UNACCEPTABLE, BULKY, ETC. METHOD!
                                        
here.open)                        
no, actually...                  
                                        
Well, first of all, why is all this - purely for
single-frame scroller. and for Simplified
shell code. maybe this is for you too
to nothing. it is even possible that you have
the need to leaf through 60 kb texts. clear-
but what about any sprites and stacks?
and you don’t want to hear. and done correctly
bark.                                  
                                        
if you want single-frame, then
You have 2 ways: Store text as ld
and push or store it as a sprite.     
                                        
in fact, memory consumption in these methods is
Yes, it turns out to be approximately the same. by-
because the text consists of letters. and
small letters predominate there, having
HEIGHT 5 pixels. thus example-
but 3/8 of the total memory volume is under-
of the text shown by the image are zeros.
two zeros can be output with one command -
push bc, for example.                      
                                        
in addition, the colors in the text change too
not very often.  i.e., roughly speaking, in
each line will have 30 more identical numbers
attribute byte.  which you canwithdraw
like this:                                    
                                        
LD HL,COLOR                     
.15 PUSH HL                         
                                        
further. all sequences of commands
push hl or push bc long, for example,
15 commands can be replaced by subroutines.
those.  put instead of themCALL PUSH15. and
Already 30 identical bytes in the image
we will spend only 3 bytes in the program
output.                                 
                                        
on average, our program will underestimate
the mother of memory is only 20-50 percent
more than the image of the text, the Temple
nothing like a sprite.  however, to deduce
sprite to frame without expanded loops
no way either. and these expanded cycles Fak-
TICALLY ELIMINATES THE ADVANTAGE IN THOSE
most 20-50 percent.                  
                                        
well, approximately)                          
                                        
at the same time, pouring over the stack, we do not
limited by font size (height)
(when the text is stored and output as
sprite, usually only 6 lines are drawn from
8,otherwise just Fi-                    
physically impossible to keep up in                  
Frame). we can also- 
Click paste into 
text sprites.        
                      
like this >>> 
:) 
approximately.. 
 
you just need to remember, 
that they should not 
be too big - 
mi.  and in general, with 
about text design 
SHOULD BE CONSIDERED, 
that you don’t need too much 
saturate the text in one- 
nom place.            
                      
вот.)