commit eb4c742e530df3371d9f5d75c7c0de72e930713f
parent 65002283bcbbb00cdcfa2560fe4390dee9204de2
Author: viznut_web <viznut_web@web>
Date: Thu, 30 Jun 2022 19:11:42 +0200
typo
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Forth.mdwn b/Forth.mdwn
@@ -2,7 +2,7 @@
The main benefit of Forth is that it is very small. A classical Forth system takes the roles of the compiler, the editor and the operating system while completely fitting in a memory space of less than 20 kilobytes. The smallness also makes it possible to implement a Forth system from scratch in a weekend.
-Forth is usually run with a two-stack [[virtual machine]], so it is much slower than compiled code. However, classical Forth system typically also include an [[assembler]] that can be used to implement speed-critical parts of the program.
+Forth is usually run with a two-stack [[virtual machine]], so it is much slower than compiled code. However, classical Forth systems typically also include an [[assembler]] that can be used to implement speed-critical parts of the program.
Most programmers see Forth as quite esoteric in comparison to other languages. Forth also doesn't "protect" the programmer from its inner peculiarities – even though it is possible to create abstractions, it is not advisable to forget what lies under those abstractions.
