The document discusses the "Rule of Least Power", which suggests choosing the least powerful language suitable for a given purpose when designing computer systems. It provides examples of where this principle has been successful, such as with HTML, CSS, JSON, and JavaScript. The document also notes that while the rule of least power is useful, the chosen language still needs to be capable of getting the job done, and may not apply to every problem.

1. The rule of least power
Do you agree?
Warning: this slide is somewhat opinionated

2. What is it?
• Tim Berners-Lee
• 1998 http://www.w3.org/DesignIssues/Principles.html
• 2006 http://www.w3.org/2001/tag/doc/leastPower.html
• When designing computer systems, one is often faced with a choice
between using a more or less powerful language for publishing
information, for expressing constraints, or for solving some problem.
• The "Rule of Least Power" suggests choosing the least powerful
language suitable for a given purpose.

3. An old blog by this guy
• 2007 Jeff Atwood
• http://blog.codinghorror.com/the-principle-of-least-power/
• He said 7 years ago
• any application that can be written in JavaScript, will eventually be written in
JavaScript.
• Did you see it coming?

4. Where this law has been successful?
• HTML
• CSS
• JSON
• Javascript
• Browser app v.s. Desktop app
• Facebook Openstack
• IBM Openpower
• Raspberry PI
• Configuration files

5. Keep In mind
• Still have to get the job done
• Not suitable for every problem, but probably more than we think