Perma/Computing/.net/Programming Languages
- #Basic Idea
- principles of #Permaculture should compel one to consider the energy impact of programming language choice or even microchip choices
- When assessing programming languages, we should pay attention to
- 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?
- 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 them?
- How fast and compact is the generated code? What are the overheads and mandatory dependencies like? Does the hello world require bytes, kilobytes, megabytes or gigabytes of memory if all the dependencies are included?
- Asking "what is the most suitable programming language for permacomputing?" is akin to asking what is "the most suitable plant for permaculture". The entire question contradicts itself.
- Not all software needs to last for decades, run efficiently or be ultra-secure. However, it is still good if the language does not prevent this.
- See also