commit 97ae16144c2c7861cead4815e773f0031316521a
parent bb3296f0eacb4597c837716f0b44601d2976bd68
Author: viznut_web <viznut_web@web>
Date: Thu, 2 Jun 2022 15:25:03 +0200
Diffstat:
1 file changed, 1 insertion(+), 0 deletions(-)
diff --git a/programming_languages.mdwn b/programming_languages.mdwn
@@ -3,6 +3,7 @@ Asking "what is the most suitable programming language for permacomputing?" is a
Here are some questions worth asking about a programming language from the resource and longevity points of view:
* How complex is the language? How long would it take to learn all the syntactical details? How long would it take to implement a compiler/interpreter from scratch?
+* How mature is the language? Do changes to the specification often break backwards compatibility? How much hacking does it require to compile and run a decades-old program in current implementations of the language?
* Are there several alternative implementations of the language? (It is generally a good sign if there are)
* What are the [[software]] characteristics of these implementations (e.g. disk and memory footprint and compilation speed)? How much resources would it take to [[bootstrap|bootstrapping]] them?
* What kind of platforms do these implementations target? Is it possible to port a program to a very small and/or obscure device without switching to another language?
