Draft article not currently submitted for review. This is a draft Articles for creation (AfC) submission. It is not currently pending review. While there are no deadlines, abandoned drafts may be deleted after six months. To edit or make changes to this draft, simply click on the "Edit" tab at the top of the window. To be accepted, a draft should: Show the subject qualifies for a Wikipedia article by using multiple sources that meet four criteria. The sources should be (1) reliable (2) secondary (3) independent of the subject (4) talk about the subject in some depth. For some topics, there are alternative criteria. Be written from a neutral point of view Respect copyright and do not plagiarize. Do not copy-paste. It is strongly discouraged to write about either yourself or your business or employer. If you do so, you must declare it. Where to get help If you need help editing or submitting your draft, please ask us a question at the AfC Help Desk or get live help from experienced editors. These venues are only for help with editing and the submission process, not to get reviews. If you need feedback on your draft, or if the review is taking a lot of time, you can try asking for help on the talk page of a relevant WikiProject. Some WikiProjects are more active than others so a speedy reply is not guaranteed. How to improve a draft Wikipedia:Contributing to Wikipedia – a basic overview on how to edit Wikipedia. Help:Wikitext – how to use the markup Help:Referencing for beginners – how to include references Wikipedia:Article development – how to develop your article Wikipedia:Writing better articles – how to improve your article Wikipedia:Verifiability – make sure your article includes reliable third-party sources You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Add tags to your draft Editor resources Easy tools: Citation bot (help) | Advanced: Fix bare URLs Last edited by PhotographyEdits (talk | contribs) 13 days ago. (Update) Submit the draft for review!

Permacomputing is a computing design philosophy which aims to improve the resilience by using regenerative design in computer and network technology. It is inspired by permaculture.^[1] Permacomputing approaches to computing often involve paying more attention to the life-cycle of hardware (including re-use and designing for older hardware),^[1] using low-level languages such as FORTH to facilitate that and foster a more mindful relationship with technology.^[2]

Permacomputing was coined by Finnish artist and writer Ville-Matias “Viznut’’ Heikkilä^[3] in an essay on their website, although it has earlier roots in a talk given by Kent Beck titled "Programming as a garden: Permaprogramming",^[4] as well as Amanda Starling Gould's 2017 doctoral dissertation on "Digital Environmental Metabolisms"^[5] which treats digital networking as a kind of geography.

Permacomputing generally centers on a set of principles^[6]:

• Hope for the Best, Prepare for the Worst: designing for resilience even when you do not expect issues;
• Care for All Hardware — Especially the Chips: pay attention to the digital foundations of technology and aim to avoid producing waste;
• Observe First: assess what is valuable, beautiful, and necessary before taking action;
• Not Doing: do not assume that technological progress is necessarily beneficial;
• Expose The Seams: make the meaning, motivation, and materiality of software design tangible and visible;
• Consider Carefully The Interaction Between Simplicity, Complexity and Scale: do not assume that a simple system is necessarily better, and avoid scaling up for its own sake;
• Keep It Flexible: make systems adaptable to different purposes and circumstances;
• Build On Solid Ground: avoid becoming strongly dependent on systems, platforms, or formats that may change rapidly;
• (Almost) Everything has a place: avoid thinking of the history of technology as a linear story of progress and obsolescence, and value diversity;
• Integrate Biological And Renewable Resources: encourage the greater integration of computational resources with sustainable and renewable materials.

A design principle in line with permacomputing is the self-obviating system,^[7] which is a system which intends to render itself unnecessary.^[8] In this paradigm, abandonment of the technology does not represent failure; for example, users may abandon a digital exercise system because they move onto other forms of exercise, like running outdoors or attending a gym, so that the system becomes unnecessary to them.

• Hundred Rabbits, an art collective working in the tradition of permacomputing
• Solarpunk