back in the day any coder had to know how his code used the hw in order to get the most bang per buck, forth is an example of that, you could get a version for the sinclairs & the other machines of that era
in those days a compiler was a compiler, you didn't quibble.
but i was referring to not so much compiler opts but you knew how efficient certain functions were in terms of cycles & RAM usage so sometimes you had functions that you really avoided
@dekkzz76@drewdiver The variety of commercial compilers for same languages and performance comparisons doesn't lend me the same impression.
I also think that Forth might abstract enough over a given CPU's assembly that having a clear idea of cycles isn't always trivial unless you implementation specifically comes with an architecture-specific reference manual that documents that.
@dekkzz76@drewdiver Yeah, individuals had little choice in the matter anyway due to price, but there were competitors to Turbo Pascal (most significantly more costly though, which is considerable considering it wasn't itself cheap to start with).
Add comment