In programming, the rule of least power is a design principle that "suggests choosing the least powerful [computer] language suitable for a given purpose".^[1] Stated alternatively, given a choice among computer languages, classes of which range from descriptive (or declarative) to procedural, the less procedural, more descriptive the language one chooses, the more one can do with the data stored in that language.

This rule is an application of the principle of least privilege to protocol design.^[2] The Rule of Least Power is an example in context of the centuries older principle known as Occam's razor in philosophy. In particular, arguments for and against the Rule of Least Power are subject to the same analysis as for Occam's razor.^{[citation needed]}

Originally proposed as an axiom of good design, the term is an extension of the KISS principle applied to choosing among a range of languages ranging from

• the plainly descriptive ones (such as the content of most databases, or progressive enhancement on the web),
• logical languages of limited propositional logic (such as access control lists),
• declarative languages on the verge of being Turing-complete,
• those that are in fact Turing-complete though one is led not to use them that way (XSLT, SQL),
• those that are functional and Turing-complete general-purpose programming languages, to
• those that are "unashamedly imperative".^[1]

As explained by Tim Berners-Lee:^[3]

Computer Science in the 1960s to 80s spent a lot of effort making languages that were as powerful as possible. Nowadays we have to appreciate the reasons for picking not the most powerful solution but the least powerful. The reason for this is that the less powerful the language, the more you can do with the data stored in that language. If you write it in a simple declarative form, anyone can write a program to analyze it in many ways. The Semantic Web is an attempt, largely, to map large quantities of existing data onto a common language so that the data can be analyzed in ways never dreamed of by its creators. If, for example, a web page with weather data has RDF describing that data, a user can retrieve it as a table, perhaps average it, plot it, deduce things from it in combination with other information. At the other end of the scale is the weather information portrayed by the cunning Java applet. While this might allow a very cool user interface, it cannot be analyzed at all. The search engine finding the page will have no idea of what the data is or what it is about. The only way to find out what a Java applet means is to set it running in front of a person.

• Worse is better